New Resource: azurerm_api_management_api_operation
#3121
Merged
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.
This PR introduces a new resource for API Management Operations, as a part of #1177
After spending /a long time/ with the nested sets, I ended up porting most elements (header, response etc) to Lists, since the API appears to be consistent in it's ordering which is helpful to avoid 3-level deep nested sets. There's also a TODO here to add an additional acceptance test when API Management Schema's are supported, but it's fine for now.
Tests pass: