Retrieve SOA record using DNS zone instead of building it from record name (#188)

<!-- This change is generated by MagicModules. -->
/cc @matco
This commit is contained in:
The Magician 2019-02-15 15:49:13 -08:00 committed by Alex Stephen
parent c77e75f5d1
commit e08e0e6f2b
2 changed files with 1 additions and 5 deletions

View file

@ -84,7 +84,6 @@ options:
managed_zone:
description:
- Identifies the managed zone addressed by this request.
- Can be the managed zone name or id.
- 'This field represents a link to a ManagedZone resource in GCP. It can be specified
in two ways. First, you can place in the name of the resource here as a string
Alternatively, you can add `register: name-of-resource` to a gcp_dns_managed_zone
@ -144,7 +143,6 @@ target:
managed_zone:
description:
- Identifies the managed zone addressed by this request.
- Can be the managed zone name or id.
returned: success
type: str
'''
@ -364,7 +362,7 @@ def prefetch_soa_resource(module):
{
'type': 'SOA',
'managed_zone': module.params['managed_zone'],
'name': '.'.join(name),
'name': replace_resource_dict(module.params['managed_zone'], 'dnsName'),
'project': module.params['project'],
'scopes': module.params['scopes'],
'service_account_file': module.params['service_account_file'],

View file

@ -43,7 +43,6 @@ options:
managed_zone:
description:
- Identifies the managed zone addressed by this request.
- Can be the managed zone name or id.
- 'This field represents a link to a ManagedZone resource in GCP. It can be specified
in two ways. First, you can place in the name of the resource here as a string
Alternatively, you can add `register: name-of-resource` to a gcp_dns_managed_zone
@ -90,7 +89,6 @@ items:
managed_zone:
description:
- Identifies the managed zone addressed by this request.
- Can be the managed zone name or id.
returned: success
type: str
'''