Document snapshot repositories at deployment level on ECE #4611
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.
ECE snapshot repositories documentation only covered creating repositories at platform level, used by ECE for automatic snapshots of the deployments (
found-snapshots).ECE users could also configure repositories directly at deployment level, independently of the automatic snapshots handled by the platform.
This PR covers that use case by linking ECE users to the ECH specific docs for custom snapshot repositories, which cover the exact use case that ECE is missing in the docs.
Closes #1494
@shainaraskas , before checking with ECE PMs I'd to get your review.
I also update the applies_to tags and include a note in the 3 ECH affected documents that now can be used by ECE.
/manage-data/migrate.mdwhen it says: