Option to run a Docker container for Opsicle commands #162
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Using the debian:jessie-slim image reduces the startup time for opsicle commands. It should be almost as fast as using the executable. |
newzac
approved these changes
Feb 11, 2021
|
|
Has QA approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Adding the option to run opsicle commands in a controlled environment.
Why
Local developer environments change frequently and this is a way to maintain it runs the same every time without having to do wrestle with your local.
Deploy Plan
n/a
Rollback Plan
git revert -m 1 MERGE_SHAand perform another deploy.URLs
n/a
QA Plan
docker build . -t dev/opsicle:latest~10 minopsicle ssh staging(in applicable repo)