Skip to content

Conversation

@ocofaigh
Copy link
Contributor

@ocofaigh ocofaigh commented Oct 28, 2025

Description

Any key that is used for backup encryption also requires the "Authorization Delegator" role. This is also stated in the docs:
image

NOTE: I expect upgrade test fail but won't skip it until its confirmed auth policy will be update in place

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

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.

@ocofaigh
Copy link
Contributor Author

/run pipeline

@ocofaigh
Copy link
Contributor Author

/run pipeline

Copy link
Contributor

@shemau shemau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is trivial, can we drop the word backup from the main encryption key in both places.

source_service_name = "databases-for-elasticsearch"
source_resource_group_id = module.resource_group.resource_group_id
roles = ["Reader"]
roles = ["Reader", "Authorization Delegator"] # Authorization Delegator role required for backup encryption key
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not the backup key.

@ocofaigh
Copy link
Contributor Author

ocofaigh commented Oct 28, 2025

@shemau They could be the backup key. If user doesn't explicitly pick a different key for backup, then the same one used for data encryption is used. Hence why I added to both policies

@ocofaigh
Copy link
Contributor Author

/run pipeline

1 similar comment
@ocofaigh
Copy link
Contributor Author

ocofaigh commented Nov 3, 2025

/run pipeline

@shemau shemau self-requested a review November 3, 2025 15:22
Copy link
Contributor

@shemau shemau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ocofaigh ocofaigh merged commit fbaef92 into main Nov 3, 2025
2 checks passed
@ocofaigh ocofaigh deleted the delegate branch November 3, 2025 16:56
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 2.4.6 🎉

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