New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update bootstrap script in light of installer refactorings #3592
Conversation
Thanks for the pull request! Here is what will happen next:
Thank you for contributing! |
The recent refactoring of our installation logic (#3344) inadvertently broke our bootstrap installation logic. Apparently, the earlier logic pulled dependent hart files from the same directory as the hart file being installed. In the new logic, it does not do this, but pulls everything from Builder through the artifact cache. The solution here is simply to place all the artifacts into the cache before installing the desired packages, just as we do with the public signing keys. True, we end up with some additional packages in our artifact cache, but that's fine. Besides, once we implement #3499, we can even clean those up. Fixes #3591 Signed-off-by: Christopher Maier <cmaier@chef.io>
e7ab1b1
to
a206e27
Compare
@thesentinels approve |
🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests. |
@thesentinels approve |
🤘 I am testing your branch against master before merging it. We do this to ensure that the master branch is never failing tests. |
Travis CI has started testing this PR. |
💖 Travis CI reports this PR passed. It always makes me feel nice when humans approve of one anothers work. I'm merging this PR now. I just want you and the contributor to answer me one question: |
The recent refactoring of our installation logic (#3344) inadvertently
broke our bootstrap installation logic. Apparently, the earlier logic
pulled dependent hart files from the same directory as the hart file
being installed. In the new logic, it does not do this, but pulls
everything from Builder through the artifact cache.
The solution here is simply to place all the artifacts into the cache
before installing the desired packages, just as we do with the public
signing keys. True, we end up with some additional packages in our
artifact cache, but that's fine. Besides, once we implement #3499, we
can even clean those up.
Fixes #3591