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
Chef Workstation version: 24.8.1068
Chef Infra Client version: 18.5.0
Chef InSpec version: 5.22.55
Chef CLI version: 5.6.14
Chef Habitat version: 1.6.1041
Test Kitchen version: 3.6.0
Cookstyle version: 7.32.8
Environment:
macOS & Ubuntu Linux
Scenario:
When a cookbook artifact has resource fork files (start with ._) the policies generated using these cookbooks differ based on the OS of the system generating them.
e.g. When a mac decompresses these files they are integrated into the filesystem, but when a Linux or Windows system decompresses them, they are left in the repo, and read for the sha
Version:
Chef Workstation version: 24.8.1068
Chef Infra Client version: 18.5.0
Chef InSpec version: 5.22.55
Chef CLI version: 5.6.14
Chef Habitat version: 1.6.1041
Test Kitchen version: 3.6.0
Cookstyle version: 7.32.8
Environment:
macOS & Ubuntu Linux
Scenario:
When a cookbook artifact has resource fork files (start with
._
) the policies generated using these cookbooks differ based on the OS of the system generating them.e.g. When a mac decompresses these files they are integrated into the filesystem, but when a Linux or Windows system decompresses them, they are left in the repo, and read for the sha
Steps to Reproduce:
Expected Result:
Expected the two policies to match exactly
Actual Result:
on a mac the policyfile.lock.json contains
on that system the cached cookbook looks like this
on a linux system the policy contains
on linux the cached cookbook looks like this
the additional
._
files seem to be the causeThe text was updated successfully, but these errors were encountered: