-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support to store service credentials in sm #411
Conversation
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
…store-service-credentials
/run pipeline |
… each other in documentation
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are new inputs that lead to new resources being created, but there are no new outputs.
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
@shemau I made the changes here consistent with this PR(terraform-ibm-modules/terraform-ibm-event-notifications#266) |
/run pipeline |
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are new variables in the DA, so I was expecting these to be exposed via /ibmcatalog.json
/run pipeline |
/run pipeline |
/run pipeline |
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
It is still concerning that the DAs are diverging.
🎉 This PR is included in version 1.15.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
#408
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
This enhancement will enable users to store service credentials in an existing secrets manager for Redis instance. Users can choose to use an existing secret group or create a new one for the service credentials.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module. --->
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers