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.

Sign up for GitHub

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

Jump to bottom

BICEP: Key Vault naming is not globally unique #830

Closed
chbragg opened this issue Jan 30, 2024 · 0 comments · Fixed by #831
Closed

BICEP: Key Vault naming is not globally unique #830

chbragg opened this issue Jan 30, 2024 · 0 comments · Fixed by #831
Assignees
@jamasten
Labels
bug Something isn't working

Comments

@chbragg
Copy link
Contributor

chbragg commented Jan 30, 2024

Description

Steps to Reproduce

Deploy MLZ to two different tenants (test and prod). There's a conflict with the key vault as the name is not unique enough to be globally unique. Naming values should be calculated similar to the storage accounts.
@chbragg chbragg added the bug Something isn't working label Jan 30, 2024
@jamasten jamasten linked a pull request Jan 31, 2024 that will close this issue
Updated key vault name for global uniqueness #831
Merged
@jamasten jamasten self-assigned this Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamasten jamasten

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Updated key vault name for global uniqueness Azure/missionlz
2 participants
@chbragg @jamasten