Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

Don't include chef-provisioning and friends in the appbundle for the … #1428

Merged
merged 1 commit into from
Oct 13, 2017

Conversation

thommay
Copy link
Contributor

@thommay thommay commented Oct 13, 2017

…kitchen executable.

Rebase of #1316

…kitchen executable.

Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
@thommay thommay requested a review from a team October 13, 2017 10:02
@thommay thommay merged commit 929385c into master Oct 13, 2017
@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
@tas50 tas50 deleted the tm+nk/less_kitchen_bundle branch March 7, 2018 00:25
@lamont-granquist
Copy link
Contributor

For posterity's sake, this never worked, and we're still shipping the same appbundler pins as we did before this:

% cat /opt/chefdk/bin/kitchen
[...]
  gem "chef-provisioning", "= 2.7.4"
  gem "chef-provisioning-aws", "= 3.0.7"
  gem "chef-provisioning-fog", "= 0.26.3"

The --without argument to the three-argument version of appbundler is only applied to the crazy transitive Gemfile.lock stuff, and is designed to keep stuff like the github-changelog-generator in the chef-dk Gemfile.lock from conflicting with the one in the berkshelf Gemfile when they're mixed together.

It affects this file:

/opt/chefdk/embedded/lib/ruby/gems/2.5.0/gems/berkshelf-7.0.7/.appbundler-gemfile20190227-93370-84j06u.lock

And is only applied in the test phase of jenkins, it has zero effect on the gems shipping in the omnibus build or the binstubs themselves.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants