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
I would like to use extract_local to extract a tarball without the "creates" property. Since the tar cookbook does not yet support true idempotence for extracted resources, In my particular case, I wish the extract to occur with every run. This way if the source tarball is changed, the new resources will be unpacked. However, omitting the 'creates' property causes the extract_local action to do nothing.
Steps to Reproduce:
Have a tar.gz file on the local filesystem, i.e. /tmp/test/tar/gz
use the tar_extract resource with the extract_local action, without a creates property
Expected Result:
tar_extract executed the extraction on every chef run
Actual Result:
tar_extract does nothing
The text was updated successfully, but these errors were encountered:
@gr33ngiant112 the way I work around it is to simply have a create property of something I know for sure is not in the package (like a ignore_me file or something). That way, the test always fails and the archive is always exploded.
Cookbook version
2.2.0
Chef-client version
12.14.60
Platform Details
Amazon Linux 2018.03 - AWS
Scenario:
I would like to use extract_local to extract a tarball without the "creates" property. Since the tar cookbook does not yet support true idempotence for extracted resources, In my particular case, I wish the extract to occur with every run. This way if the source tarball is changed, the new resources will be unpacked. However, omitting the 'creates' property causes the extract_local action to do nothing.
Steps to Reproduce:
Have a tar.gz file on the local filesystem, i.e. /tmp/test/tar/gz
use the tar_extract resource with the extract_local action, without a creates property
Expected Result:
tar_extract executed the extraction on every chef run
Actual Result:
tar_extract does nothing
The text was updated successfully, but these errors were encountered: