Open hashibot opened 7 years ago
cookbook_constraints { .... }
Can someone give me an example of how cookbook_constraints
is formatted? I looked through the docs and searched for examples and could not find any.
For example if I wanted to constrain the cookbook "chef-vault" to be greater than "1.0", what would be the formatting to define that?
@planet
"cookbook": "~> 1.0.0"
for instance is cookbook as key, value includes a version constraint operator plus a semver version. Constraint operators can be many, but include things like pessimistic greater (~>), equality, greater than, less than, greater than or equal, etc. You get the idea.
This issue was originally opened by @mengesb as hashicorp/terraform#13696. It was migrated here as part of the provider split. The original body of the issue is below.
I believe this started with 0.8.x series, though it's tough to recall. I had initially pawned this off as configuration drift, however on nearly every invocation of terraform, I'm seeing a diff operation on the
chef_environment
resource. While I can't see anything immediately different, it's always determining a diff and thus my destroy provisioner executes. Even when I run subsequent applies one right after the other, it detects a diff and must re-upload the environment and fire the triggered resource.Terraform Version
0.9.2
Affected Resource(s)
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Debug Output
Small snipped segment shows the diff is
nil
, which is where i think it has the problem.Panic Output
None
Expected Behavior
Subsequent runs where no environment attributes change result in no diff, and no action, and no trigger firing
Actual Behavior
Nearly always, there's a computed diff and thus the trigger fires
Steps to Reproduce
terraform apply
terraform apply
Important Factoids
Nothing comes to mind
References
None