-
Notifications
You must be signed in to change notification settings - Fork 15
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
feat: initial commit for DA #915
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it is still under development, but I left a few comments to make sure we address them. We should talk about the variation name. simple
is probably not what we will go with
I created this draft PR with the intent of early review. Thanks for this. Yes, name will be changed once we decide. |
Currently,
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We really need to make use of cross variable validation in the variables.tf file. For example, if person sets kms_encryption_enabled_bucket
or enable_vpc_flow_logs
then other inputs become required.
Also question - should we support creating VPEs? Or are we planning to have a standalone VPE DA? (cc @vburckhardt )
@maheshwarishikha FYI these are the variation names we will go with:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- As per our most recent discussions, we should no longer support creating a resource group, but instead we should require an existing resource group name (using input
existing_resource_group_name
).- We can still use our terraform-ibm-resource-group module in the code to return the resource group ID.
- We should use the catalog resource group picker in the ibm_catalog.json for this input:
{ "key": "existing_resource_group_name", "custom_config": { "type": "resource_group", "grouping": "deployment", "original_grouping": "deployment", "config_constraints": { "identifier": "rg_name" } } }
- Add support for VPE (using https://github.com/terraform-ibm-modules/terraform-ibm-vpe-gateway)
- Add support for VPN (see current code at https://github.com/terraform-ibm-modules/terraform-ibm-landing-zone/blob/main/vpn.tf)
/run pipeline |
/run pipeline |
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/run pipeline |
"label": "[Add-ons Beta] Cloud automation for VPC", | ||
"product_kind": "solution", | ||
"tags": [ | ||
"network_vpc", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maheshwarishikha This is a subcategory tag. We are missing a main category tag. I'm going to add the network
tag or it will prevent us from publishing. FYI you can see all tags by running ibmcloud catalog filter options --all
ibm_catalog.json
Outdated
"ibm_created", | ||
"target_terraform", | ||
"terraform", | ||
"support_ibm", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maheshwarishikha I think we need to remove this and add the ibm_beta
tag. We are not supporting this tile via IBM Cloud - its only experimental beta
/run pipeline |
🎉 This PR is included in version 7.21.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
VPC DA - fully configurable variant
Issue: https://github.ibm.com/GoldenEye/issues/issues/12217
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers