-
Notifications
You must be signed in to change notification settings - Fork 339
RDSC-5669 Publish RDI Cloud API reference #3562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ZdravkoDonev-redis
wants to merge
10
commits into
main
Choose a base branch
from
rdsc-5669-rdi-capi-docs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
3c25bf9
RDSC-5669 publish RDI Cloud API reference
ZdravkoDonev-redis 8c0a01d
RDSC-5669 refresh RDI API reference
ZdravkoDonev-redis be6f28d
RDSC-5669 merge RDI API into Cloud reference
ZdravkoDonev-redis 86d3d10
RDSC-5669 link Cloud RDI docs to API reference
ZdravkoDonev-redis 40737bc
RDSC-5669 move RDI API links to contextual pages
ZdravkoDonev-redis 26e52a3
RDSC-5669 add RDI pipeline payload example
ZdravkoDonev-redis 5125139
RDSC-5669 refresh RDI API reference
ZdravkoDonev-redis f3a46cb
RDSC-5669 document RDI workspace schemas
ZdravkoDonev-redis 58a3a8b
RDSC-5669 make RDI API reference reproducible
ZdravkoDonev-redis 63e664e
RDSC-5669 fetch RDI OpenAPI from docs endpoint
ZdravkoDonev-redis File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is all of this stuff added here and is not part of the rdi json file in the first place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The goal was that CAPI exposes functionality not just of the cloud database but all applications as well. So for example, the RDI API is accessible under the CAPI Pro subscriptions path, so on one side it makes sense to document the RDI API in the same place.
If you think we should separate the docs reference, we can also discuss that approach.
TBH I don't have a strong opinion.