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

scylla-node/Debian_install.yml: Don't check if the installed scylla v… #375

Conversation

vladzcloudius
Copy link
Collaborator

…ersion appears in the repo exactly once

We have a check that validates that a value in scylla_version matches exactly one (full) scylla verison from the repository so that the Role can install it.

However this check is only relevant when we are going to install anything, and when scylla is already installed - we are not going to. Hence, this check is only making noise in such a case.

One common example of such a situation is when a custom build is installed.

@vladzcloudius vladzcloudius force-pushed the allow_scylla_version_with_custom_build branch from 7571f4b to 287bf80 Compare May 10, 2024 20:52
…ersion appears in the repo exactly once unless we are upgrading

We have a check that validates that a value in `scylla_version` matches exactly one (full) scylla verison
from the repository so that the Role can install it.

However this check is only relevant when we are going to install anything, and when scylla is already
installed and we are not upgrading - we are not going to. Hence, this check is only making noise in such a case.

One common example of such a situation is when a custom build is installed.

Signed-off-by: Vlad Zolotarov <[email protected]>
@vladzcloudius vladzcloudius force-pushed the allow_scylla_version_with_custom_build branch from 287bf80 to 011fb2c Compare May 10, 2024 20:54
@vladzcloudius vladzcloudius merged commit ce50d11 into scylladb:master May 11, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants