-
Notifications
You must be signed in to change notification settings - Fork 197
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
poc: c8 migration manual #4557
poc: c8 migration manual #4557
Conversation
👋 🤖 🤔 Hello, @christinaausley! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
Thanks for starting with this already, @christinaausley, appreciate it 👍 |
@tmetzke I made some formatting adjustments -- let me know what you think 👍 |
@tmetzke Could you have a look over this draft and add any required adjustments to merge for a first draft? |
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.
👍 Really cool, @christinaausley, I like the tab idea so we get a comprehensive list of endpoints and for each of them you can browse the changes bit by bit.
💭 Let's see how this looks like when we have more endpoints in here but we can adjust 🦖
Co-authored-by: Tobias Metzke-Bernstein <[email protected]>
958f531
to
2859f66
Compare
docs/apis-tools/administration-api/administration-api-reference.md
Outdated
Show resolved
Hide resolved
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.
Since the intention of this PR is to merge and keep iterating, the only blocking change I have is the note in the Admin API since it's not part of the V1 APIs or the migration to the C8 REST API.
docs/apis-tools/administration-api/administration-api-reference.md
Outdated
Show resolved
Hide resolved
…e.md Co-authored-by: Amara Graham <[email protected]>
Camunda is streamlining the developer experience by creating a unified REST API for Zeebe, Operate, Tasklist, and the Identity components with endpoint parity. This will be a single REST API for the orchestration cluster for a consistent and intuitive API experience to help your teams develop process automation solutions faster. | ||
|
||
:::note | ||
The Administration and Web Modeler APIs will not be part of the Camunda 8 REST API, as these are platform APIs outside the cluster’s scope. |
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.
We'll need to refine what "cluster" means, but we have not settled on clear definitions. See #4648.
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.
I'm ok with this as a first increment to merge! 👍
🧹 Preview environment for this PR has been torn down. |
Description
Relates to camunda/camunda#23736.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).