Add up.sh and down.sh development scripts for consistency with other ansible operators #1991
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
…ansible operators
rooftopcellist
force-pushed
the
dev-scripts
branch
from
1a2ecba
to
2d328ee
Compare
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.
SUMMARY
Contributing my development scripts made generic. These are consistent with the ones in the eda-server-operator repo as well, and largely the same as the galaxy-operator repo.
ISSUE TYPE
ADDITIONAL INFORMATION
Usage examples:
Build operator image from your local checkout, push to quay.io/youruser/awx-operator:dev, and deploy operator.
Cleanup and delete the namespace you deployed in.
export NAMESPACE=awx ./down.sh