You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon instantiation of new VPC, the following resources are generated automatically:
default Network ACL
default Security Group
default Routing Table
Given the affected resources cannot handle updates to names of existing resources in an account (as the name is used to identify the resource), it is not possible to use these resources to update the auto-naming with a hyphenated list of randomly-selected words.
Alternatively, an easier implementation may be to update the VPC resource ibm_is_vpc with resource arguments for updating the naming of these immediately after they are automatically created. For example:
Affected Resource(s)
Please list the resources as a list, for example:
ibm_is_vpc
ibm_is_network_acl
ibm_is_security_group
ibm_is_vpc_routing_table
Missing capability
Upon instantiation of new VPC, the following resources are generated automatically:
Given the affected resources cannot handle updates to names of existing resources in an account (as the name is used to identify the resource), it is not possible to use these resources to update the auto-naming with a hyphenated list of randomly-selected words.
Alternatively, an easier implementation may be to update the VPC resource
ibm_is_vpc
with resource arguments for updating the naming of these immediately after they are automatically created. For example:Which subsequently can be used in a data resource to identify the resource in the account, and apply Security Group rules etc.
Related issues
#2203
Important Factoids
IBM Cloud APIs with PATCH call is the current mechanism to update naming using the resource identifiers:
The text was updated successfully, but these errors were encountered: