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

[OC-1082]: migration script to work even if px-backup is disabled and for external ls server. #320

Open
wants to merge 1 commit into
base: 2.1.0
Choose a base branch
from

Conversation

diptiranjanpx
Copy link
Contributor

signed-off-by: Diptiranjan

What this PR does / why we need it:

  1. Migration script to work even if px-backup is not installed and with external LS server.
  2. Changes to support 2.1.0 migration.

… for external ls server.

          Changes to support 2.1.0 migration.
current_px_central_version="2.0.0"
fi

# job_imagetag
if [ $current_px_central_version == "2.0.1" ]; then
# TODO: Needs to modify to public tags in 2.0.1 final patch
if [ $current_px_central_version == "2.1.0" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of using else if can we use an array or list of the version that is supported and check for that.
In long run this will keep adding to the complexity, a better solution would be to say we support all versions ahead of 2.0.0

@@ -496,8 +500,8 @@ if [ "$helmvaluesfile" != "" ]; then
fi

if [ "$px_central_version" != "" ]; then
if [ $px_central_version != "2.0.0" ] && [ $px_central_version != "2.0.1" ]; then
echo "upgrade-version can only be 2.0.1 or 2.0.0"
if [ $px_central_version != "2.1.0" ] && [ $px_central_version != "2.0.1" ] && [ $px_central_version != "2.0.0" ]; then
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These supported versions should be in an array or a list.

@diptiranjanpx diptiranjanpx added the invalid This doesn't seem right label Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants