Camunda 8 Run authentication warning

[mesellings]

Description

This PR provides further temporary fixes to help resolve the Camunda 8 Run/REST API authentication issue.

• Changed the warning to a caution, and reworded to remove limitation language and other components.
• Additionally, fixed link format and typo

This does not address further changes required for this authentication issue, as detailed in the relevant Slack channel, namely:

To access the REST API (v1 or v2) you need to make use of the Cookie auth setup by the webapps and we need to document that too.

Once that documentation is complete, we should revisit these pages and change the caution link to point to the new auth documentation.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 🤔 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/.

• docs/self-managed/setup/deploy/local/local-kubernetes-cluster.md

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.

[megglos]

LGTM! Thanks @mesellings for taking action here right away 🚀

[conceptualshark]

Suggested change

	Due to a bug in 8.6, use the Spring Zeebe SDK version `8.5.0`.
	The Spring Zeebe SDK is currently pinned to version `8.5.0`.

^ If we'd like to remove the bug language, we can just note that it's currently set at 8.5 (and therefore required).

[romansmirnov]

I shared my feedback on Slack already, so I disagree with having such a caution so prominent because it behaves as expected and the Camunda REST API is not really mentioned or used in the guides.

[romansmirnov]

IMO, this caution/warning should be removed in favor of https://github.com/camunda/camunda-8-get-started-spring/pull/9/files - In a nutshell, the application.properties must be adjusted to make it work.

[romansmirnov]

The same as above.

[romansmirnov]

Being honest, to me this does not make sense. This installation guide does not reference the Camunda REST API at all. The page still focuses on the old architecture by talking about Zeebe configuration, gRPC endpoints, etc.

[romansmirnov]

I think the Camunda REST API is not referenced or promoted in the guides, so why is this "caution" necessary?

[akeller]

I shared my feedback on Slack already, so I disagree with having such a caution so prominent because it behaves as expected and the Camunda REST API is not really mentioned or used in the guides.

Thanks @romansmirnov. We also have instructions to work with C8Run that may be for non-getting started users. We've softened this quite a bit and removed the admonition so people are proactively informed.

[akeller]

Based on the conversations in the Zoom, this looks like it satisfies feedback in a way that centers the developer experience without being too shouty.

[github-actions]

🧹 Preview environment for this PR has been torn down.