forked from rook/rook
Satoru Takeuchi
b585c35743
Mark overwriting Ceph's configurations as breaking changes. This is to avoid troubles caused by such changes on upgrade. ref. https://github.com/rook/rook/discussions/16652 Signed-off-by: Satoru Takeuchi <satoru.takeuchi@gmail.com>
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
<!-- Thank you for contributing to Rook! -->
|
|
|
|
<!-- STEPS TO FOLLOW:
|
|
1. Add a description of the changes (frequently the same as the commit description)
|
|
2. Enter the issue number next to "Resolves #" below (if there is no tracking issue resolved, **remove that section**)
|
|
3. Review our Contributing documentation at https://rook.io/docs/rook/latest/Contributing/development-flow/
|
|
4. Follow the steps in the checklist below, starting with the **Commit Message Formatting**.
|
|
-->
|
|
|
|
<!-- Uncomment this section with the issue number if an issue is being resolved
|
|
**Issue resolved by this Pull Request:**
|
|
Resolves #
|
|
--->
|
|
|
|
**Checklist:**
|
|
|
|
- [ ] **Commit Message Formatting**: Commit titles and messages follow guidelines in the [developer guide](https://rook.io/docs/rook/latest/Contributing/development-flow/#commit-structure).
|
|
- [ ] Reviewed the developer guide on [Submitting a Pull Request](https://rook.io/docs/rook/latest/Contributing/development-flow/#submitting-a-pull-request)
|
|
- [ ] [Pending release notes](https://github.com/rook/rook/blob/master/PendingReleaseNotes.md) updated with breaking and/or notable changes for the next minor release.
|
|
- Overwriting Ceph's configurations should be marked as breaking changes.
|
|
- [ ] Documentation has been updated, if necessary.
|
|
- [ ] Unit tests have been added, if necessary.
|
|
- [ ] Integration tests have been added, if necessary.
|