-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
add build.name to hcl code #10114
add build.name to hcl code #10114
Conversation
Codecov Report
|
6ce745e
to
d895b0b
Compare
}, | ||
fileCheck: fileCheck{ | ||
expected: []string{ | ||
"pineapple.pizza.txt", |
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.
haha
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.
Super good work ! The provisioner re-prepare probably made this a bit harder to dev as the value was overwritten !
If/when we go with an implementation where things are prepared only whey they are about to be launched (HCL2Core) then this will be a bit simpler 🙂 .
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Build name and Source name are not the same thing in HCL -- while users can name builds, they previously had not way of accessing the buildname in variables. This adds a "name" key to the build accessor so that users can read out this var.
This checks off a box in #9176