-
Notifications
You must be signed in to change notification settings - Fork 43
Adds isolated instance mode description #5136
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
The ```isolated:true``` option moves the instance to RO mode In this mode, various debugging & maintanance operations can be performed Fixes #4632
Fixes language and syntax
doc/code_snippets/snippets/config/instances.enabled/isolated_mode/config.yaml
Outdated
Show resolved
Hide resolved
|
|
||
| See also: :ref:`configuration_labels` | ||
|
|
||
| .. _configuration_reference_isolated_mode: |
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.
Forgot to say it on the previous review iteration: AFAIR, options/sections on each level are sorted alphabetically. Here isolated goes after labels.
| Since version :doc:`3.3.0 </release/3.3.0>`, a new ``isolated`` option is added to instance configuration. | ||
|
|
||
| The option takes boolean values, by default it is set to ``false``. | ||
| ``isolated:true`` moves the instance it has been applied at to the **isolated** mode. |
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.
Nit: isolated: true looks better for me (comparing to isolated:true).
Totktonada
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.
Thank you for working on it!
isolated:trueoption moves the instance to RO modeFixes config: isolated mode for an instance #4632