-
Notifications
You must be signed in to change notification settings - Fork 1
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
refactor!: Namegenerator functions refactor #12
Conversation
🎉 Thanks for opening this pull request! We really appreciate contributors like you! 🙌 |
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.
Great job, thank you for refactoring code and doing 1 function (instead multiple ones per cloud) 👍
Besides below comments, I have also 1 more question - what is the reason to pass PROJECT_ID
via Terratest skeleton , do not change anything in that value and return it in struct TerraformVarsInfo
? Maybe we could directly get project ID in tests in repository terraform-google-vmseries-modules
, without passing that value into skeleton and reading it from outputs ?
Co-authored-by: Sebastian Czech <[email protected]>
Co-authored-by: Sebastian Czech <[email protected]>
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.
great job 👍
please change PR title from refactor:
into refactor!:
as we have breaking change.
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.
👍
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.
👍🏻
🎉 Congrats on getting your first pull request merged! We here at Palo Alto Networks are so grateful! ❤️ |
Description
Refactor Name Generator function into a single function. Also introduce obtaining GCP project ID based on repo secrets environment variables.
This PR closes #9 .
Motivation and Context
Code refactoring.
How Has This Been Tested?
Tested using separate test repo : https://github.com/PaloAltoNetworks/test-gcp-ci-workflows/ .
Tested by pointing the GO module to the specific branch .
Types of changes
Checklist