-
Notifications
You must be signed in to change notification settings - Fork 183
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
Update camunda REST API doc #4427
Conversation
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.
Considering the large amount of changes here, not very many for me to carry upstream 💪
get: | ||
tags: | ||
- User task | ||
summary: Return user task by a user task key. |
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.
summary: Return user task by a user task key. | |
summary: Return user task by a user task key |
❌ no periods in summary
owner: me in an upstream PR
@@ -441,6 +441,58 @@ paths: | |||
schema: | |||
$ref: "#/components/schemas/ProblemDetail" | |||
/user-tasks/{userTaskKey}: | |||
get: | |||
tags: | |||
- User task |
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.
Not sure which one, but either this one or the next endpoint are going to need to change, for consistency. (The next one is tagged with User Task
, in title case.)
owner: me
$ref: "#/components/schemas/FlowNodeInstanceItem" | ||
"400": | ||
description: > | ||
The flow node instance Get failed. |
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 flow node instance Get failed. | |
The flow node instance request failed. |
owner: me
$ref: "#/components/schemas/DecisionDefinitionItem" | ||
"400": | ||
description: > | ||
The decision definition Get by key failed. |
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 decision definition Get by key failed. | |
The decision definition request failed. |
owner: me
$ref: "#/components/schemas/DecisionRequirementsItem" | ||
"400": | ||
description: > | ||
The decision requirements Get failed. |
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 decision requirements Get failed. | |
The decision requirements request failed. |
owner: me
get: | ||
tags: | ||
- Decision requirements | ||
summary: Get decision requirements XML (alpha). |
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.
summary: Get decision requirements XML (alpha). | |
summary: Get decision requirements XML (alpha) |
owner: me
type: string | ||
"400": | ||
description: > | ||
The decision requirements Get XML failed. |
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 decision requirements Get XML failed. | |
The decision requirements request failed. |
owner: me
The decision instance search successful response. | ||
"202": | ||
description: | | ||
The Authorization was patched successfully. |
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 Authorization was patched successfully. | |
The authorization was patched successfully. |
owner: me
The Authorization was patched successfully. | ||
"400": | ||
description: | | ||
The Authorization could not be patched. |
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 Authorization could not be patched. | |
The authorization could not be patched. |
owner: me
format: date-time | ||
endDate: | ||
processDefinitionId: | ||
description: Process defintion id of this process definition. |
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.
description: Process defintion id of this process definition. | |
description: Process definition id of this process definition. |
owner: me
@pepopowitz, would you like to add the changes here and create an upstream PR to "manifest" them? Or just create the upstream PR and update here after merging it? |
I will merge this one as-is, and then open a PR upstream, so that the next sync corrects them all. I don't mind these things sitting in vNext for a week. |
👋 🤖 🤔 Hello! 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. |
🧹 Preview environment for this PR has been torn down. |
…cs (#23595) ## Description This PR addresses a few small C8 REST API spec issues, most of which were identified in camunda/camunda-docs#4427. There are a few extra changes that were identified from pattern-matching the issues in 4427. See camunda/camunda-docs#4427 for original conversation on these changes.
Description
This is an autogenerated PR by the sync api specs workflow.
This PR contains every changes made to the REST api specs in the monorepo in the last week.
This PR contains also all the generated OpenAPI files related to the changes.
When should this change go live?
PR Checklist
/docs
directory (aka/next/
).