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
Given the above stacker.yaml, run stacker build once, change the content of 'import1.txt' and then run it again. Expectation is that the build would be redone.
stacker version
v1.0.0-rc5-396ff9d liblxc cb8e38aca27a23964941f0f011a8919aab8bebab
Describe the bug
When using import with a destination, stacker does not realize that a imported file has changed and re-build the content.
Given the above stacker.yaml, run
stacker build
once, change the content of 'import1.txt' and then run it again. Expectation is that the build would be redone.To reproduce
I am attaching a script to automate the testing.
stacker-test.sh.txt
Expected behavior
Build should occur a second time, after import1.txt content is changed and log should contain output showing that it built.
Screenshots
Example output
Additional context
No response
The text was updated successfully, but these errors were encountered: