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 key-vault name length constraint #71

Merged
merged 1 commit into from
Mar 10, 2023

Conversation

eternaltyro
Copy link
Contributor

Azure Key Vault names are universally unique.

To make sure there are no name collisions with the new production Key-Vault, a random_pet resource was used as a prefix. But Azure Key Vault has a constraint for name length (8-24 chars). To fix it, random_string is being used instead of random_pet. The string length is set to 3 to accommodate long project names and deployment environment labels.

Azure Key Vault names are universally unique.

To make sure there are no name collisions with the new production
Key-Vault, a random_pet resource was used as a prefix. But Azure Key
Vault has a constraint for name length (8-24 chars). To fix it,
random_string is being used instead of `random_pet`. The string length is
set to 3 to accommodate long project names and deployment environment
labels.
@eternaltyro eternaltyro added bug Something isn't working infrastructure Don't let it crumble.. labels Mar 10, 2023
@eternaltyro eternaltyro self-assigned this Mar 10, 2023
@eternaltyro
Copy link
Contributor Author

Commit will destroy and create two resources. (and create key vault fresh)

@eternaltyro eternaltyro merged commit 12dca54 into develop Mar 10, 2023
@eternaltyro eternaltyro deleted the fix/key-vault-namespace-length-constraint branch March 10, 2023 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working infrastructure Don't let it crumble..
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant