Skip to content

doc: clarifies checkfilechanges option use case (not intended for plugin)#1180

Merged
joergsteffens merged 2 commits intobareos:masterfrom
bruno-at-bareos:dev/bruno/master/doc-checkfilechange-t5161
Jun 23, 2022
Merged

doc: clarifies checkfilechanges option use case (not intended for plugin)#1180
joergsteffens merged 2 commits intobareos:masterfrom
bruno-at-bareos:dev/bruno/master/doc-checkfilechange-t5161

Conversation

@bruno-at-bareos
Copy link
Contributor

@bruno-at-bareos bruno-at-bareos commented May 11, 2022

This PR is about clarifying the option CheckFileChanges usage in documentation.
It will clearly state this option is reserved for File= resource type, and has to not be used with Plugin=

Referenced in bug #1452 and bug #1449

Please check

  • Short description and the purpose of this PR is present above this paragraph
  • Your name is present in the AUTHORS file (optional)

If you have any questions or problems, please give a comment in the PR.

Helpful documentation and best practices

Checklist for the reviewer of the PR (will be processed by the Bareos team)

General
  • PR name is meaningful
  • Purpose of the PR is understood
  • Separate commit for this PR in the CHANGELOG.md, PR number referenced is same
  • Commit descriptions are understandable and well formatted
Source code quality
  • Source code changes are understandable
  • Variable and function names are meaningful
  • Code comments are correct (logically and spelling)
  • Required documentation changes are present and part of the PR
  • bareos-check-sources --since-merge does not report any problems
  • git status should not report modifications in the source tree after building and testing

@bruno-at-bareos bruno-at-bareos changed the title doc: clarify checkfilechange option use case (not intended for plugin) doc: clarify checkfilechanges option use case (not intended for plugin) May 11, 2022
@pstorz pstorz requested a review from joergsteffens May 19, 2022 09:17
@arogge arogge self-assigned this Jun 9, 2022
Copy link
Member

@joergsteffens joergsteffens left a comment

Choose a reason for hiding this comment

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

We also discussed to fix the behavior when using plugin filesets. Any progress on this? If yes, maybe this change is not required at all.

@bruno-at-bareos
Copy link
Contributor Author

We also discussed to fix the behavior when using plugin filesets. Any progress on this? If yes, maybe this change is not required at all.

I've not yet seen any new PR for that. Do you want to put this PR on hold ?

@bruno-at-bareos bruno-at-bareos changed the title doc: clarify checkfilechanges option use case (not intended for plugin) doc: clarifies checkfilechanges option use case (not intended for plugin) Jun 20, 2022
bruno-at-bareos and others added 2 commits June 22, 2022 15:03
…lugin

Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
Co-authored-by: Jörg Steffens <joergsteffens@users.noreply.github.com>
Signed-off-by: Bruno Friedmann <bruno.friedmann@bareos.com>
@bruno-at-bareos bruno-at-bareos force-pushed the dev/bruno/master/doc-checkfilechange-t5161 branch from 780cbb0 to ee6574d Compare June 22, 2022 13:05
@joergsteffens joergsteffens merged commit a97809a into bareos:master Jun 23, 2022
@bruno-at-bareos bruno-at-bareos deleted the dev/bruno/master/doc-checkfilechange-t5161 branch July 4, 2022 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants