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

pip dns needs to be unique for esri enterprise #963

Closed
mikedzikowski opened this issue Apr 4, 2024 · 0 comments · Fixed by #964
Closed

pip dns needs to be unique for esri enterprise #963

mikedzikowski opened this issue Apr 4, 2024 · 0 comments · Fixed by #964
Assignees
@mikedzikowski
Labels
bug Something isn't working

Comments

@mikedzikowski
Copy link
Contributor

Description

pip dns needs to be unique for esri enterprise

Steps to Reproduce

Steps to reproduce the behavior:

  1. deploy esri enterprise across two subs using the same identifier

Expected behavior

pip dns name created is unique

Actual behavior

pip dns name is not unique if same identifier is supplied at deployment

Screenshots

Additional context

Operating System:
Terraform Version:
Cloud (public, Azure Government, etc.):
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikedzikowski mikedzikowski

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

Successfully merging a pull request may close this issue.

add pip unique dns name and update container for artifacts in mgmt vm Azure/missionlz
1 participant
@mikedzikowski