fix: service credential source service role #273
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Issue: #268
Reported in terraform-ibm-modules/terraform-ibm-cos#817, the logic for creating the service credential only worked for roles where the CRN service-name was 'iam'. Syncing this module with the secret module, to expose terraform-ibm-modules/terraform-ibm-secrets-manager-secret#249.
Additional changes are included in examples/complete to cover creating an arbitrary service credential (using event notifications since the service already existed in the example).
The DA does not support secret creation, so that is does not change with this release. This release updates both the main module and the fscloud sub module which permit the creation of secrets.
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
The inputs for the main module and fscloud sub module change. The secrets block, for secrets of secret_type 'service_credentials' that previously set 'service_credentials_source_service_role', now need to set 'service_credentials_source_service_role_crn'. The CRN for the role to give the service credential in the source service. These can be looked up at https://cloud.ibm.com/iam/roles, select the service and select the role to view the CRN for that role.
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