-
Notifications
You must be signed in to change notification settings - Fork 213
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
Bundle script for Offline Installation of Porter #3205
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for the PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do understand the change you are implementing here, but I'm a little concerned about the complexity it adds to the installation script.
Also preferably it should be implemented for the Powershell installation script.
Would it be possible for you to join the community meeting, so we can discuss the different options here? The next community meeting is on Thursday
* The plugin logger should use verbosity level The log level is meant to be used only for log files. Signed-off-by: Kim Christensen <[email protected]> * Correctly detect log level from plugin logs The constants used before was numbers, causing the writing to always fall back to writing as debug Signed-off-by: Kim Christensen <[email protected]> * Correct the documentation Signed-off-by: Kim Christensen <[email protected]> * Do not log information messages from the plugin infrastructure Signed-off-by: Kim Christensen <[email protected]> --------- Signed-off-by: Kim Christensen <[email protected]> Co-authored-by: schristoff <[email protected]> Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Signed-off-by: John Cudd <[email protected]>
Closed in favor of #3210 |
What does this change
Give a summary of the change, and how it affects end-users. It's okay to copy/paste your commit messages.
The new
bundle-linux.sh
script automates the creation of a tarball containing all the necessary artifacts for installing the Porter CLI, including the MongoDB Docker image and the Porter installation files. It pulls a specific version of the MongoDB image and packages all the downloaded assets into a compressed tarball, providing clear instructions for extracting the bundle and executing the installation script. This makes it easy for users to set up Porter in air-gapped environments.The
install-linux.sh
script has been updated to handle offline installations by installing local binaries and the MongoDB image if they are present. It now checks for the existence of themongo_image.tar
file, loads the MongoDB image into Docker, and runs a MongoDB container during installation if it is not already running. Additionally, the script allows the use of a localporter-linux-amd64
binary if it is available, allowing for an fully offline installation.What issue does it fix
Closes #3198
Notes for the reviewer
The
bundle-linux.sh
script pulls the latest version of theinstall-linux.sh
from the CDN, so when testing you will need to replace the downloadedinstall-linux.sh
file with the one from this branch.Checklist