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

Fix backup field name in scylla cluster spec documentation #1056

Merged

Conversation

shivamarora1
Copy link
Contributor

as per this doc https://operator.docs.scylladb.com/stable/scylla_cluster_crd.html, the correct key is backups

Description of your changes:

Which issue is resolved by this Pull Request:
Resolves #

Copy link
Collaborator

@zimnx zimnx left a comment

Choose a reason for hiding this comment

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

/lgtm

@scylla-operator-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: shivamarora1, zimnx

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@scylla-operator-bot scylla-operator-bot bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 18, 2023
@zimnx zimnx changed the title fix: corrected backup key name in scylla cluster spec Fix backup field name in scylla cluster spec documentation Aug 18, 2023
@zimnx zimnx added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 18, 2023
@scylla-operator-bot scylla-operator-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 18, 2023
@tnozicka
Copy link
Member

/retest

@scylla-operator-bot scylla-operator-bot bot merged commit c688f71 into scylladb:master Aug 23, 2023
26 of 36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants