Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enhancement: ibm_is_vpc arguments for naming of default Network ACL, Security Group and Routing Table #2216

Closed
sean-freeman opened this issue Jan 30, 2021 · 2 comments
Assignees
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure

Comments

@sean-freeman
Copy link

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:

  • 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:

default_network_acl_name
default_security_group_name
default_routing_table_name

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:

@astha-jain
Copy link
Contributor

PR is merged. Can this issue be closed? @hkantare

@kavya498
Copy link
Collaborator

Available in latest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants