Skip to content
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

fix: service credential source service role #273

Merged
merged 1 commit into from
Jan 24, 2025
Merged

fix: service credential source service role #273

merged 1 commit into from
Jan 24, 2025

Conversation

shemau
Copy link
Contributor

@shemau shemau commented Jan 23, 2025

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?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (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:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

@shemau shemau requested a review from alex-reiff as a code owner January 23, 2025 13:14
@shemau
Copy link
Contributor Author

shemau commented Jan 23, 2025

/run pipeline

@ocofaigh ocofaigh merged commit 8899dc0 into main Jan 24, 2025
2 checks passed
@ocofaigh ocofaigh deleted the role-crn branch January 24, 2025 09:07
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 1.22.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants