Clarify DNS record resource_group_name usage in documentation. #4455
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.
For most resources, the resource_group_name attribute is used to specify the group
into which the new resource will be added. In the case of DNS records, the resource_group_name
specifies the group in which the parent can be found.
I had a DNS Zone in one resource group, and was attempting to create a CNAME record in a different resource group (as though that were possible). This wasn't working - 404 error indicated that the parent resource could not be found. When I realised that the resource_group_name attribute was used to locate the DNS Zone, rather than to select which group the new resources should be placed in, it all worked.
I wonder whether my proposed changes to the documentation might help others in future.