-
Notifications
You must be signed in to change notification settings - Fork 64
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 of key vault import and late initialization #536
Conversation
Import also works properly, see #479 (comment) |
* Fix key vault import * Use special function to keep name + version as part of externalname so it will have a format of `key-name/84faa4674826492e9b16095719740a00` * Fixes crossplane-contrib#479 Co-authored-by: Sergen Yalçın <yalcinsergen97@gmail.com> Signed-off-by: Yury Tsarev <yury@upbound.io>
a05462d
to
1e353ba
Compare
Signed-off-by: Yury Tsarev <yury@upbound.io>
1e353ba
to
e005e9d
Compare
/test-examples="examples/keyvault/keyvault-all-in-one.yaml" |
@turkenf just to note it here, the uptest is failing with access issues |
/test-examples="examples/keyvault/secret.yaml" |
/test-examples="examples/keyvault/key.yaml" |
/test-examples="examples/keyvault/vault.yaml" |
/test-examples="examples/keyvault/key.yaml" |
f162c21
to
5055f8d
Compare
- azurerm_key_vault - azurerm_key_vault_key - azurerm_key_vault_certificate
5055f8d
to
af65763
Compare
* Update example with known working configuration * Remove manual intervention Signed-off-by: Yury Tsarev <yury@upbound.io>
/test-examples="examples/keyvault/certificate.yaml" |
Certificate is actually good. We need to adjust uptest datasource for proper AccessPolicy config in the pipeline. CC @turkenf @jeanduplessis |
/test-examples="examples/keyvault/certificate.yaml" |
3 similar comments
/test-examples="examples/keyvault/certificate.yaml" |
/test-examples="examples/keyvault/certificate.yaml" |
/test-examples="examples/keyvault/certificate.yaml" |
0071e02
to
bdddecf
Compare
/test-examples="examples/keyvault/key.yaml" |
bdddecf
to
b3b8cb4
Compare
/test-examples="examples/keyvault/key.yaml" |
b3b8cb4
to
a8d1bac
Compare
/test-examples="examples/keyvault/secret.yaml" |
a8d1bac
to
0aedb3c
Compare
All uptest runs passed successfully and I added them to the description. I also did an upgrade test and created the
Then I updated the provider according to this PR and updated
We need to document this in the next release. |
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.
Thanks @ytsarev LGTM!
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.
Thank you @ytsarev, LGTM.
Description of your changes
keyVaultURLIDConf
with the ability to properly keep id ofkeyName/$uuid_version
within the externalName. Courtesy of @sergenyalcinrotationPolicy
is not specified: the late init ofrotation_policy
Certificate
observe and deletion issues #20I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Tested both fresh Key creation and the import. Tested creation with and without
rotation_policy
. All green. The uptest will follow.Uptest:
Certificate.keyvault
: https://github.com/upbound/provider-azure/actions/runs/6246579398Key.keyvault
: https://github.com/upbound/provider-azure/actions/runs/6248424448Secret.keyvault
: https://github.com/upbound/provider-azure/actions/runs/6248497316