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

Azure traffic manager profile hash is not sufficiently unique #232

Closed
philbrookes opened this issue Sep 13, 2024 · 0 comments · Fixed by #235
Closed

Azure traffic manager profile hash is not sufficiently unique #232

philbrookes opened this issue Sep 13, 2024 · 0 comments · Fixed by #235
Assignees

Comments

@philbrookes
Copy link
Contributor

philbrookes commented Sep 13, 2024

The hash generated for traffic manager profiles is not being calculated correctly and as such is not sufficiently unique.

@philbrookes philbrookes self-assigned this Sep 13, 2024
@philbrookes philbrookes converted this from a draft issue Sep 13, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 16, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 16, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 16, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 17, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 18, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 18, 2024
philbrookes added a commit to philbrookes/dns-operator that referenced this issue Sep 18, 2024
github-merge-queue bot pushed a commit that referenced this issue Sep 18, 2024
gh-232: traffic manager profile hash generation update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant