apimanagement: pulling the location field from the API rather than the local config during deletion
#22752
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
… config The config isn't necessarily available during the Delete, so we cannot rely on this
…wouldn't be surfaced
|
Tests look fine 👍 |
tombuildsstuff
added a commit
that referenced
this pull request
Aug 1, 2023
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
d.Getisn't guaranteed to return a value during the Delete methods - therefore we need to look this up from the Remote API instead.Fixes https://github.com/hashicorp/terraform-provider-azurerm/actions/runs/5712688553/job/15476668791?pr=22748