docs: upgrade docs now reflect the new upgrade commands #1331
Conversation
This file contains 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
✅ Deploy Preview for constellation-docs canceled.
|
thomasten
reviewed
Mar 3, 2023
thomasten
approved these changes
Mar 3, 2023
Co-authored-by: Thomas Tendyck <[email protected]>
Since we now have a config value called microserviceVersion it hopefully makes it easier for users to understand what this value controls if we also use the term microservice in the docs.
derpsteb
force-pushed
the
feat/upgrade-docs
branch
from
9187ce4
to
c2959ca
Compare
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.
Proposed change(s)
component(s)withmicroservice(s)when referring to our microservices. Since users are now faced with a config value calledmicroserviceVersion, I feel like something should come up when searching the docs for "microservice".Checklist