Update references to upstream CAPI Operator documentation #65
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
Danil-Grigorev
requested review from
furkatgofurov7,
richardcase and
salasberryfin
salasberryfin
previously approved these changes
Mar 12, 2024
Danil-Grigorev
force-pushed
the
ref-to-upstream-capi-operator-docs
branch
from
99dfe2c to
a2ca1e1
Compare
Signed-off-by: Danil Grigorev <[email protected]>
furkatgofurov7
approved these changes
Mar 12, 2024
salasberryfin
approved these changes
Mar 12, 2024
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.
We need to remove stale parts of the documentation related to raw CAPI Operator operations, as the user is expected to use CAPIProvider resource in all cases. This adds a reference to the upstream docs where possible, to keep the users in sync with changes.