community.general.hwc_vpc_peering_connect module – Creates a resource of Vpc/PeeringConnect in Huawei Cloud
Note
This module is part of the community.general collection (version 7.5.2).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.general
.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.general.hwc_vpc_peering_connect
.
New in community.general 0.2.0
Synopsis
vpc peering management.
Aliases: cloud.huawei.hwc_vpc_peering_connect
Requirements
The below requirements are needed on the host that executes this module.
keystoneauth1 >= 3.6.0
Parameters
Parameter |
Comments |
---|---|
The description of vpc peering connection. |
|
The name of the Domain to scope to (Identity v3). (currently only domain names are supported, and not domain IDs). |
|
The id of resource to be managed. |
|
The Identity authentication URL. |
|
Specifies the ID of local VPC. |
|
Specifies the name of the VPC peering connection. The value can contain 1 to 64 characters. |
|
The password to login with. |
|
Specifies information about the peering VPC. |
|
Specifies the ID of the project which the peering vpc belongs to. |
|
Specifies the ID of peering VPC. |
|
The name of the Tenant (Identity v2) or Project (Identity v3). (currently only project names are supported, and not project IDs). |
|
The region to which the project belongs. |
|
Whether the given object should exist in Huawei Cloud. Choices:
|
|
The timeouts for each operations. Default: |
|
The timeouts for create operation. Default: |
|
The user name to login with (currently only user names are supported, and not user IDs). |
Attributes
Attribute |
Support |
Description |
---|---|---|
Support: full |
Can run in |
|
Support: none |
Will return details on what has changed (or possibly needs changing in |
Notes
Note
For authentication, you can set identity_endpoint using the
ANSIBLE_HWC_IDENTITY_ENDPOINT
env variable.For authentication, you can set user using the
ANSIBLE_HWC_USER
env variable.For authentication, you can set password using the
ANSIBLE_HWC_PASSWORD
env variable.For authentication, you can set domain using the
ANSIBLE_HWC_DOMAIN
env variable.For authentication, you can set project using the
ANSIBLE_HWC_PROJECT
env variable.For authentication, you can set region using the
ANSIBLE_HWC_REGION
env variable.Environment variables values will only be used if the playbook values are not set.
Examples
# create a peering connect
- name: Create a local vpc
hwc_network_vpc:
cidr: "192.168.0.0/16"
name: "ansible_network_vpc_test_local"
register: vpc1
- name: Create a peering vpc
hwc_network_vpc:
cidr: "192.168.0.0/16"
name: "ansible_network_vpc_test_peering"
register: vpc2
- name: Create a peering connect
community.general.hwc_vpc_peering_connect:
local_vpc_id: "{{ vpc1.id }}"
name: "ansible_network_peering_test"
peering_vpc:
vpc_id: "{{ vpc2.id }}"
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
The description of vpc peering connection. Returned: success |
|
Specifies the ID of local VPC. Returned: success |
|
Specifies the name of the VPC peering connection. The value can contain 1 to 64 characters. Returned: success |
|
Specifies information about the peering VPC. Returned: success |
|
Specifies the ID of the project which the peering vpc belongs to. Returned: success |
|
Specifies the ID of peering VPC. Returned: success |