Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Expose versionFingerprint instead of versionId from packer template #12803
Expose versionFingerprint instead of versionId from packer template #12803
Changes from 3 commits
10d7aed
dea4b66
bc682b6
8168a8f
de1ec54
868450b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 log here will be problematic, the context is used for evaluating HCL expressions, and we create it often.
The fact that
iterationID
exists does not mean it is used, that happens in other places.Note: it may not be trivial to figure out with certainty that it's used, as evaluation is done by the HCL library, outside of Packer's code.
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.
That will make
iterationID
unusable in this state unfortunately, since we create the object in this branch, and we do the same above, so this assignation will erase the previous value.I would suggest changing a couple of things here, the previous approach is probably not valid anymore.
Let's remove the creation of the
packerAccessor
object from the declaration of the context, we can build it along the way, and only create it when it is in its final state.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'm not sure we can suggest using
versionFingerprint
without encouraging them to update the data sources that use it at the same time.I would maybe reword this here so it explains the rationale behind the 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.
I wonder, does that work? I'm not certain the fingerprint will be instanciated by the time we evaluate this.
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.
To be clear if it doesn't we should fix it later, but I'm cautious giving this example if it doesn't work
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 should update the logs here so they don't show the
hcp_iteration_id
in there right?