-
Notifications
You must be signed in to change notification settings - Fork 3
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: add functionality to pass a custom name for the vpe gateway #362
Conversation
/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.
The implementation in the main module looks fine.
I would question the whole second example.
During CI tests both others_tests and pr_tests are going to run. Resulting in a second example test that is identical other the names on 3 out of 18 VPE gateways.
The new example code sets and passes the new variable and other_test.pr sends a value. I wonder if a better solution would be to put that code in the existing example and have it called from pr_test with the new map?
My thought is that the coverage is the same, both the old (default name, on 15 of 18 gateways) and the new (passed name, on 3 of 18 gateways) would be tested covering both code paths. This is achieved with only one VPC and ICD instance. Resource consumption is lower and the opportunity to fail is lower (VPC tear down has been a bit flaky at times).
Co-authored-by: Renovate Bot <renovate@whitesourcesoftware.com>
Co-authored-by: Renovate Bot <renovate@whitesourcesoftware.com>
Co-authored-by: Renovate Bot <renovate@whitesourcesoftware.com>
…terratest-wrapper to v1.10.17 (#365) Co-authored-by: Renovate Bot <renovate@whitesourcesoftware.com>
Given the above feedback, I've removed the Output from main
Output from vpe-name
|
/run pipeline |
SKIP UPGRADE TEST upgrade test fails due to new variable being passed to the test, skipping
/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
🎉 This PR is included in version 2.7.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Description
Add a new variable to allow for passing a map containing keys which match the service name for which a VPE Gateway will be created corresponding to a value which is the name you want that gateway to have. Example and test for this functionality also created.
Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.
x.x.X
)x.X.x
)X.x.x
)Release notes content
Add the ability to customize the names of the Gateways being created by the module, in order to pass a name assign a map to
var.vpe_names
whose keys are the services which you want to have a custom gateway name for, and the corresponding values are the names you want to assign to those gateways.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
Merge actions for mergers