fix premature exit when RG doesn't exist (#46013)
* fixes #45941
* corrects regression introduced by #26104; when the resource group doesn't exist, the module exits prematurely with an error instead of creating it.
(cherry picked from commit 3b52d968e6
)
This commit is contained in:
parent
135b85e0b7
commit
25f656413d
2 changed files with 4 additions and 1 deletions
2
changelogs/fragments/azure_rm_deployment_fix_45941.yaml
Normal file
2
changelogs/fragments/azure_rm_deployment_fix_45941.yaml
Normal file
|
@ -0,0 +1,2 @@
|
|||
bugfixes:
|
||||
- azure_rm_deployment - fixed regression that prevents resource group from being created (https://github.com/ansible/ansible/issues/45941)
|
|
@ -491,7 +491,8 @@ class AzureRMDeploymentManager(AzureRMModuleBase):
|
|||
|
||||
if self.append_tags and self.tags:
|
||||
try:
|
||||
rg = self.get_resource_group(self.resource_group_name)
|
||||
# fetch the RG directly (instead of using the base helper) since we don't want to exit if it's missing
|
||||
rg = self.rm_client.resource_groups.get(self.resource_group_name)
|
||||
if rg.tags:
|
||||
self.tags = dict(self.tags, **rg.tags)
|
||||
except CloudError:
|
||||
|
|
Loading…
Reference in a new issue