You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
Currently, it's not possible to use the variable build.name in a post-processor but it's possible to use build.ID, or at least it doesn't throw an error.
The same goes for other variables on build like Host, User or Password.
Simple example:
source"null""first-example" {
communicator="none"
}
build {
name="step1"sources=["null.first-example"]
provisioner"shell-local" {
# Worksinline=["echo ${build.name}"]
}
post-processor"shell-local" {
# Error: Unsupported attribute; This object does not have an attribute named "name".inline=["echo ${build.name}"]
}
}
Use Case(s)
My use case is the following, I would like to be able to use the build.name in the filename of the generated manifest.
This way I would only have to maintain one value at one place.
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.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
Currently, it's not possible to use the variable
build.name
in a post-processor but it's possible to usebuild.ID
, or at least it doesn't throw an error.The same goes for other variables on
build
likeHost
,User
orPassword
.Simple example:
Use Case(s)
My use case is the following, I would like to be able to use the
build.name
in the filename of the generated manifest.This way I would only have to maintain one value at one place.
Potential configuration
None
Potential References
The pull request which added the variable in provisioner: #10114
The text was updated successfully, but these errors were encountered: