goldyfruit / goldyfruit.ibmcloud_automation / 1.0.4 / module / ic_is_vpc Manage VPC (Virtual Private Cloud) on IBM Cloud. | "added in version" 2.9 of goldyfruit.ibmcloud_automation" Authors: Gaëtan Trellu (@goldyfruit) preview | supported by communitygoldyfruit.ibmcloud_automation.ic_is_vpc (1.0.4) — module
Install with ansible-galaxy collection install goldyfruit.ibmcloud_automation:==1.0.4
collections: - name: goldyfruit.ibmcloud_automation version: 1.0.4
This module creates a new VPC from a VPC prototype object. The prototype object is structured in the same way as a retrieved VPC, and contains the information necessary to create the new VPC.
- name: Create VPC ic_is_vpc: vpc: ibmcloud-vpc-baby
- name: Create VPC without default address prefixes ic_is_vpc: vpc: ibmcloud-vpc-baby address_prefix_management: manual
- name: Delete VPC ic_is_vpc: vpc: ibmcloud-vpc-baby state: absent
vpc: description: - The unique user-defined name for this VPC. required: true type: str state: choices: - present - absent default: present description: - Should the resource be present or absent. type: str classic_access: choices: - true - false default: false description: - Indicates whether this VPC should be connected to Classic Infrastructure. If true, this VPC's resources will have private network connectivity to the account's Classic Infrastructure resources. - Only one VPC, per region, may be connected in this way. This value is set at creation and subsequently immutable. type: bool resource_group: description: - The resource group to use. If unspecified, the account's default resource group is used. type: str address_prefix_management: choices: - auto - manual default: auto description: - Indicates whether a default address prefix should be automatically created for each zone in this VPC. If manual, this VPC will be created with no default address prefixes. type: str