-
Notifications
You must be signed in to change notification settings - Fork 185
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
feat(broker): update docs in backups/GCS regarding initialization and added update guide from 8.6 to 8.7 #4412
Conversation
👋 🤖 🤔 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. |
To prevent misconfiguration, Zeebe will check at startup that the specified bucket exists and can be accessed, but | ||
it will not prevent Zeebe to start up. |
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.
To prevent misconfiguration, Zeebe will check at startup that the specified bucket exists and can be accessed, but | |
it will not prevent Zeebe to start up. | |
To prevent misconfiguration, Zeebe will check at startup that the specified bucket exists and can be accessed, and log at WARN level if the bucket does not exist. |
d62450a
to
bbff0b1
Compare
…d update guide from 8.6 to 8.7
bbff0b1
to
d78a406
Compare
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: "Review which adjustments must be made to migrate from Camunda 8.6.x to Camunda 8.7.0." | ||
--- | ||
|
||
The following sections explain which adjustments must be made to migrate from Camunda 8.6.x to 8.6.x for each component. |
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.
Looks like this merged with a typo @entangled90. Please be sure to include tech-writers
in your reviewers for most docs changes.
Description
When should this change go live?
hold
label or convert to draft PR)PR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).closes #4410