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.
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
New resource
azurerm_postgresql_server_key
- Add CMK support #8126New resource
azurerm_postgresql_server_key
- Add CMK support #8126Changes from 10 commits
119d4d8
de9139d
7f40156
d623a19
d51d85d
48250f6
1f3120b
3cef967
3747ed6
ffa967a
49312f6
3e49ee9
5149e94
a6ae9df
3772185
510a9f6
1f58b13
78d9750
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Should this also support the "versionless" secrets? If so we'll likely need to look up the current version to be able to use that as a name?
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.
By saying
key_vault_key_id
, it means some key URL WITH version like this:Do you suggest we change this schema to align with the CMK for storage? i.e, like this:
to emphasize that we are requiring a versioned key here?
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.
right however most Azure API's which support a versioned secret also take a "versionless" version too (since the 'version' gets parsed as empty, which the Key Vault API's return as "latest") - so we should test that
No, this makes sense to leave as
key_vault_key_id
- however we need to confirm if this validation needs to accept both a versioned and versionless Key ID, which we'll identify through testing that?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.
Sure I will have a try with this
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.
Just have a try if we pass a key URL without version, and get an
internalServerError
.And per their document page, they should be expecting the key URL with version
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.
Then should we be validing that the id has a version then?
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.
This function
ValidateKeyVaultChildId
is expecting this ID to have a version. We have aValidateKeyVaultChildIdVersionOptional
for the version-optional scenario