-
Notifications
You must be signed in to change notification settings - Fork 33
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
Install Lagoon in all Lagoon CLI Containers #726
Comments
This would be great for a whole bunch of reasons. The primary one I'm after is being able to trigger a Our project currently has a solution to dump this to the filesystem but we have vendors who would appreciate access via the UI. |
What is the best option in your opinion:
|
@vincenzodnp I wrote my opinion in the first comment already, plus also in the header of this issue.
Not sure why we would install it only in the toolbox? as the toolbox is not used by customers it wouldn't really help them? |
Yes, installed in CLI images so that it is easy for customers to use |
@shreddedbacon - so I started playing around with this inside the containers and it looks like, by default the dynamically linked binaries don't work straight (at least in alpine). Building statically, it works just peachy. I wonder if it doesn't make sense to do a static release to support people running the cli inside containers? |
@bomoko definitely. If you want to submit a PR to update the Makefile to support static builds, I'm down for it. |
This is still planned, but are wary that inserting it into every* container might cause unwanted impacts to users who don't deploy regularly. We can provide instructions on how best to achieve it in a project. |
Is your feature request related to a problem? Please describe.
Feature Request
Describe the solution you'd like
Have
lagoon
cli already installed in all CLI Images of LagoonThe text was updated successfully, but these errors were encountered: