updates to resolve issue #794 #919
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run unit |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run update |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run unit |
1 similar comment
|
/azp run unit |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run e2e |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ATuckwell
force-pushed
the
bug/794/deploy-private-dns-zones
branch
from
4822c83
to
3b7ae45
Compare
|
/azp run unit |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview/Summary
This PR relates to an issue raised in bug #794. The issue is that the managed identity created as part of policy assignment "deploy-private-dns-zones" does not have adequate permissions to add Host A records in the relevant private DNS zone within the connectivity subscription. This change takes the managed identity principal ID and applies Private DNS Zone Contributor rights on the Connectivity management group.
This PR fixes/adds/changes/removes
#794
Breaking Changes
None
Testing Evidence
Please provide any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate).
Local testing performed with PR'd code changes with the desired outcome as below.
The Principal ID (Object ID) of the MI associated to initiative assignment.
Validation of the Object ID of the MI within Entra ID.
Confirmation that the above MI had the required perms at the Connectivity management group.
As part of this Pull Request I have
mainbranch