Add possibility to manually set privatelink partition ids for azure static apps #1061
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
Azure static web apps are currently spawned without a known pattern in Public DNS zones with different partition ids in their FQDN. We are now counting [1,2,3,4,5].azurestaticapps.net with a unknown rising number.
Private DNS Zones are used for private Endpoints correspondingly (privatelink.[1,2,3,4,5].azurestaticapps.net.) and as of the CAF principals need to be known before deploying the first resources.
There is no programmatic approach known to me.
Feel free to adjust to your needs.
Examples for module calls:
This PR fixes/adds/changes/removes
Breaking Changes
none
Testing Evidence
As part of this Pull Request I have
mainbranch