-
Notifications
You must be signed in to change notification settings - Fork 228
docs(agentic-orchestration): update get started #7649
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
Conversation
|
👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉 You can read more about the versioning within our docs in our documentation guidelines. |
| | Prerequisite | Description | | ||
| | :------------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | Camunda 8 environment | <p>To run your agent, you must have Camunda 8 (version 8.8 or newer) running, using either:</p><p><ul><li><p> [Camunda 8 Self-Managed](/self-managed/about-self-managed.md). For example, see [Run your first local project](../getting-started-example).</p></li><li><p> [Camunda 8 SaaS](/components/saas/saas.md). For example, [sign up for a free SaaS trial account](https://accounts.cloud.camunda.io/signup).</p></li></ul></p> | | ||
| | Camunda 8 environment | <p>To run your agent, you must have Camunda 8 (version 8.8 or newer) running, using either:</p><p><ul><li><p> [Camunda 8 SaaS](/components/saas/saas.md). For example, [sign up for a free SaaS trial account](https://accounts.cloud.camunda.io/signup).</p></li><li><p> [Camunda 8 Self-Managed](/self-managed/about-self-managed.md). For example, see [Run your first local project](../getting-started-example).</p></li></ul></p> | |
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.
@bojtospeter Based on our conversation, my understanding is that we want to:
- Keep AWS Bedrock as the cloud-based LLM model linked to the SaaS experience.
- Add content explaining how to use a local LLM model (e.g., Ollama, following the blog) for the Self-Managed experience.
That is, AWS for SaaS and Ollama for Self-Managed? Is this correct?
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.
@afgambin
AWS bedrock (or other cloud based LLM provider) can be used for SaaS and Self-managed as well.
local LLM can be used only for Self-managed
So self-managed users have a bit more flexibility in this sense.
|
@bojtospeter I added the tabs for SaaS vs. Self-Managed, as discussed, and left one pending question before proceeding. Have a look whenever you can. Preview here. Also, do we have a link to the new blog? Is it already published? I only have the link to the Gdoc. |
bojtospeter
left a comment
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.
This cleanup really helps to reduce noise around SaaS / SM
@afgambin |
bojtospeter
left a comment
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.
Please change the documentation for 8.8 as well, since it's applicable to 8.8 too.
|
@bojtospeter Thanks for the review! Changes have been backported. For the subsequent PR: adding instructions on how to set up the local LLM, please share the link to the published blog when it’s available. Before merging this, I’d love to hear from @mesellings, who mentioned during a meeting that there could be an issue with using tabs in this case. |
bojtospeter
left a comment
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.
LGTM
mesellings
left a comment
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.
@afgambin the tabs look fine in this - the issue is around using tabs for larger blocks of documentation (including headings within) due to a Docusaurus bug (example issue) and also not the right UX experience (we shouldn't hide important docs), so this use case is fine - only one non-blocking comment, otherwise lgtm! 🚀
|
@mesellings I’ve addressed your feedback. Can we merge it? I see you added the hold label - if so, could you please reapprove? Thanks! |
mesellings
left a comment
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.
Approved! 🚀
|
🧹 Preview environment for this PR has been torn down. |
Description
This PR updates the Get Started tutorial for Agentic Orchestration by introducing tabs for the two available working environments (SaaS vs. Self-Managed). This simplifies the tutorial and is part of this epic.
When should this change go live?
bugorsupportlabel)available & undocumentedlabel)holdlabel)low priolabel)PR Checklist
{type}(scope): {description}commit message(s)/docsdirectory (version 8.9)./versioned_docsdirectory.@camunda/tech-writersunless working with an embedded writer.