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.

Sign up for GitHub

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

Jump to bottom

Support cassandra_latest.yaml #46

Merged
merged 2 commits into from
May 30, 2024
Merged

Support cassandra_latest.yaml #46

merged 2 commits into from
May 30, 2024

Conversation

burmanm
Copy link
Collaborator

@burmanm burmanm commented May 27, 2024

If cassandra_latest.yaml is in the base config directory, use it for newer defaults. Otherwise, use the old cassandra.yaml.

Fixes #43

@burmanm burmanm force-pushed the cassandra_latest branch from 29c736c to 83b3ffd Compare May 29, 2024 14:12
rzvoncek
rzvoncek approved these changes May 29, 2024
View reviewed changes
Copy link

@rzvoncek rzvoncek left a comment

Choose a reason for hiding this comment

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

I did not manage to find an easy way to see a container with the contents of the cassandra_latest.yaml being created because I couldn't find a serverVersion to put into my spec.

However, a 4.1.4 node worked fine.

@burmanm burmanm merged commit 94540eb into k8ssandra:main May 30, 2024
2 checks passed
@burmanm
Copy link
Collaborator Author

burmanm commented May 30, 2024

This was for 5.0.0 actually, that bundles _latest.yaml. But it's fine, it's not GA yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rzvoncek rzvoncek rzvoncek approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Add support for cassandra-latest.yaml
2 participants
@burmanm @rzvoncek