metadata_strategy: extended requires 'store_by: uuid' documentation u…#22380
Open
ashtag3696 wants to merge 1 commit intogalaxyproject:devfrom
Open
metadata_strategy: extended requires 'store_by: uuid' documentation u…#22380ashtag3696 wants to merge 1 commit intogalaxyproject:devfrom
ashtag3696 wants to merge 1 commit intogalaxyproject:devfrom
Conversation
github-project-automation
bot
moved this from Needs Review
to Done
in Galaxy Dev - weeklies
github-project-automation
bot
moved this from Done
to In Progress
in Galaxy Dev - weeklies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #17694
This PR updates the documentation to clarify that when using metadata_strategy: extended, the object store configuration must include "store_by: uuid".
Note that I've updated between :::{admonition} Warning---:class: warning. Further minor formatting improvements can be addressed in follow-up changes if needed.