Skip to content
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

ses: Add ses upload subcommand (SCRD-8432) #185

Merged
merged 4 commits into from
Apr 2, 2019
Merged

Conversation

skazi0
Copy link
Member

@skazi0 skazi0 commented Mar 15, 2019

The ses upload subcommand can be used to upload yaml file with SES configuration to crowbar.

NOTE there are couple of changes included in this PR which are not strictly related to SES but rather refactoring and/or pre-requisites for actual SES commands.

@skazi0 skazi0 force-pushed the ses-commands branch 2 times, most recently from b36fa09 to 9ca7c22 Compare March 15, 2019 08:17
skazi0 added 3 commits March 18, 2019 15:06
By default it is detected based on the OS release for local machine.
If needed, it could be overridden using CROWBAR_CLOUD_VERSION environment variable.
The `ses upload` subcommand can be used to upload yaml file with
SES configuration to crowbar.
JanZerebecki
JanZerebecki previously approved these changes Mar 18, 2019
@skazi0 skazi0 requested review from jsuchome and JanZerebecki March 19, 2019 09:07
Upgrade version check was re-doing the check done for cloud_version.
Re-using this part gives added value of "passing" the override information
from `CROWBAR_CLOUD_VERSION` to upgrade subcommands.
@stefannica stefannica changed the title ses: Add ses upload subcommand ses: Add ses upload subcommand (SCRD-8432) Mar 29, 2019
@jdsn jdsn self-requested a review April 2, 2019 08:43
@skazi0
Copy link
Member Author

skazi0 commented Feb 20, 2020

Backport was not really needed as crowbar-client doesn't have per-release branches. This #196 should be enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants