fix: service credential source service role #304
Merged
+31
−36
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:
The logic for creating the service credential only worked for roles where the CRN service-name was 'iam'. Syncing this module with the secret manager module, to expose terraform-ibm-modules/terraform-ibm-secrets-manager#268 and the secret module, to expose terraform-ibm-modules/terraform-ibm-secrets-manager-secret#249.
Additional changes are included in pr_test.go to include a cloud-object-service serviceRole based service credential.
The DA does support secret creation and the internal structure of a complex variable has changed. Any consumer using this feature to create service credentials will have to replace the existing 'service_credentials_source_service_role' with the equivalent 'service_credentials_source_service_role_crn'.
This is a text input in the catalog, the content of the field will not be lost, but it will have to be updated.
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
The service_credential_secrets variable that previously set 'service_credentials_source_service_role' property in an object, now needs 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