-
Notifications
You must be signed in to change notification settings - Fork 165
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
archive(8.1) isolation: manual steps #3760
archive(8.1) isolation: manual steps #3760
Conversation
@@ -44,8 +44,8 @@ Follow these steps to configure the Amazon EventBridge Connector: | |||
- **Source**: Enter the value that identifies the service that generated the event. | |||
- **Detail type**: Enter the type of event being sent. Refer to the [Amazon documentation](https://docs.aws.amazon.com/eventbridge/latest/userguide/eb-events-structure.html) for more information on these properties. | |||
5. In the **Event Payload** section, enter a JSON object that contains information about the event. | |||
6. (Optional) In the **Output Mapping** section, you can set a **Result variable** or **Result expression**. Refer to the [response mapping documentation](/docs/components/connectors/use-connectors/index.md#response-mapping) to learn more. | |||
7. (Optional) In the **Error Handling** section, define the **Error expression** to handle errors that may occur during the event sending process. Refer to the [response mapping documentation](/docs/components/connectors/use-connectors/index.md#bpmn-errors) to learn more. | |||
6. (Optional) In the **Output Mapping** section, you can set a **Result variable** or **Result expression**. Refer to the [response mapping documentation](components/connectors/use-connectors/index.md#variableresponse-mapping) to learn more. |
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 links updated in this PR seem to be missing the first /
. I think you only want to remove /docs
.
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 intentionally removed /docs/
including slashes on both sides, because I associate markdown links that begin with a /
as typically referencing /docs
, and ending in a cross-instance link (which these don't do, but it's muscle memory I guess). I don't really have a preference since both resolve to the correct place. Is this feedback blocking?
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 blocking, just wanted to make sure it was intentional since other links in these same files are /components/
vs. components/
Description
Part of #3731.
Note that this targets the branch
unsupported/8.1
, and will never make it intomain
.Manual tasks to isolate a site for version 8.1, including:
main
in a separate PR.canonicalUrl
property, which was previously crossing versions, to target the supported location of the canonical Operate API Overview page.See #2832 for a comparable PR of a previous version (8.0).
This is the final PR for isolating version 8.1. After this is merged, I'll deploy the 8.1 version to unsupported.docs.camunda.io/8.1.
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).