azurerm_container_app
- Set resource id right after resource is created
#28513
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.
Community Note
Description
Creating the
azurerm_container_app
is an async operation, especially that the LRO part includes pulling container images, which can fail if configured incorrectly.This PR is to move up the resource set in TF right after the "sync" part of the creation succeeded and the resource record created in Azure. The benefit is that even if the LRO part later failed, users won't have to manually import and delete the resource themselves.
PR Checklist
For example: “
resource_name_here
- description of change e.g. adding propertynew_property_name_here
”Changes to existing Resource / Data Source
Testing
Change Log
Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.
azurerm_container_app
- Set resource id right after resource is created [GH-00000]This is a (please select all that apply):
Related Issue(s)
Fixes #28511
Note
If this PR changes meaningfully during the course of review please update the title and description as required.