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
If some of your apt_repository 'foo' do blocks are critical (any failure should fail the entire run), but others are non-critical (OK to ignore), you have to choose to either fail when you don't need to or continue when you wanted to fail.
This is related to the request for retry logic in #164, but I think they're distinct issues. There are reasons other than retry-fixable intermittent failures to have different ignore_failure behavior on different repositories.
We've removed the apt_update and apt_repository resources from this cookbook as they were merged into core chef. I'm going to close this issue out now. If you think it's still valid against a new chef-client release please open it up against the chef/chef repo so we can work on it where the code now resides.
Environment:
Debian
Scenario:
If some of your
apt_repository 'foo' do
blocks are critical (any failure should fail the entire run), but others are non-critical (OK to ignore), you have to choose to either fail when you don't need to or continue when you wanted to fail.Steps to Reproduce:
Expected Result:
A failure to add the juju repo shouldn't fail the build, while a failure to add the cloudera repo should.
The text was updated successfully, but these errors were encountered: