Document a new fleet_manager setting

[NataliaIvakina]

No description provided.

[NataliaIvakina]

Do we need to update the Plugins page?

[renetapopova]

Looks good. Just a minor suggestion.

[renetapopova]

I think it should be the following to be consistent with the class in the monorepo:

Suggested change

	== Fleet manager settings
	== Fleet management settings

[alexnb]

The official name of the feature changed to "Fleet manager", also, the setting has "manager" in its key. @SeBBBe, WDYT?

[SeBBBe]

I think "Fleet manager" is preferred as we've decided to rebrand the feature under that name. We also made a decision not to change the procedures, so those will still be under the fleetManagement name (in order not to have to force existing users to change their whitelisting settings etc), but we should move to the new name wherever it makes sense.

[renetapopova]

Do we need to update the Plugins page?

Yeah, I think so.

[NataliaIvakina]

Do we need to update the Plugins page?

@alexnb, which details should we add to the page ⬆️? WDYT?

[alexnb]

Do we need to update the Plugins page?

@alexnb, which details should we add to the page ⬆️? WDYT?

Maybe extending the example in the code block at the end of the page ("# to enable Fleet management ..."). I guess it would be better if @SeBBBe reviews this PR, adding him.

[SeBBBe]

It will be possible to use fleet manager either by enabling the setting documented in this PR, or by installing the fleet manager plugin (which is the current method). The plan is to enable fleet manager by default some time in Q1, at which point the plugin documentation will be obsoleted for that Neo4j version, going forward.

That means that when we do the launch of the off-by-default built-in fleet manager, we are in sort of an intermediate stage. For the Aura documentation and the copy shown in the Aura console, we've decided to keep the current copy intact (which is to install the plugin). After it's been enabled by default we'll change the copy. Otherwise we find that it becomes confusing. Does this approach make sense?

[NataliaIvakina]

It will be possible to use fleet manager either by enabling the setting documented in this PR, or by installing the fleet manager plugin (which is the current method). The plan is to enable fleet manager by default some time in Q1, at which point the plugin documentation will be obsoleted for that Neo4j version, going forward.

That means that when we do the launch of the off-by-default built-in fleet manager, we are in sort of an intermediate stage. For the Aura documentation and the copy shown in the Aura console, we've decided to keep the current copy intact (which is to install the plugin). After it's been enabled by default we'll change the copy. Otherwise we find that it becomes confusing. Does this approach make sense?

I think it makes sense, and let's keep our docs (Aura docs and the Ops manual) consistent. If I understand correctly, at the moment there is no need for user to configure this setting, or even to know a lot about this setting. A user should follow the current steps. This will be less confusing

[neo4j-docops-agent]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

[SeBBBe]

I think it makes sense, and let's keep our docs (Aura docs and the Ops manual) consistent. If I understand correctly, at the moment there is no need for user to configure this setting, or even to know a lot about this setting. A user should follow the current steps. This will be less confusing

Yes, that's correct!

[SeBBBe]

Looks good!