Composable image: Move common content into individual settings topics #4789
Conversation
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
catplat
added
docs rework
catplat
changed the title
catplat
changed the title
…iding in separate files
…common properties above the properties table
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
Feedback indicates the single-runtime image and composable image topics are too long. These two topics contains a lot of common content.
Decision: Split out the common content into separate settings topics, and keep the image-specific content in the original single-runtime image and composable image topics.
What's changed
Where are changes
Individual settings topic will eventually move to Configure apps > App reference > Image properties > .
Updates are for:
sites/platformtemplates)sites/upsuntemplates)