[Remote clusters] Add cloud-specific logic to remote clusters

[alisonelizabeth]

Fixes #61503

Changes include:

• [Cloud only] Server name is a required field
• [Cloud only] Default mode is "proxy"
• [Cloud only] Info callout added under the proxy mode switch
• [Cloud only] When editing a v1 remote cluster, a default server name will be created for the user.
• Fixed a bug related to the schema validation on update + added a test to guard against this scenario (64226f8).

How to test

To simulate a cloud environment, you can enable the cloud plugin in your kibana.dev.yml settings:

xpack.cloud.enabled: true
xpack.cloud.id: 'foo'

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[alisonelizabeth]

/cc @juliocamarero

[juliocamarero]

Thanks a ton @alisonelizabeth

@cristina-eleonora, could you please confirm the info callout makes sense to you?
You can find the proxy address and server name of your cluster in the Security section of your deployment.

[alisonelizabeth]

@elasticmachine merge upstream

[cjcenizal]

Tested locally, code LGTM! Thanks for the copious comments and for adding tests.

@juliocamarero Are there use cases for a Cloud user to use the non-proxy mode?

[alisonelizabeth]

@elasticmachine merge upstream

[alisonelizabeth]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 12bae26

History

• 💔 Build #36926 failed 463fa44
• 💔 Build #36897 failed 37c23c5
• 💔 Build #36859 failed 097d085
• 💔 Build #36827 failed b713a9c

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream