[IGNITE-19365] Disable components until the cluster configuration is applied

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: clients, rest
• Labels: ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Mikhail Pochatkin
• Reporter: Vadim Pakhnushev
• Created: 25/Apr/23 14:56
• Updated: 27/Dec/23 14:41
• Resolved: 27/Dec/23 14:41

Description

There are instances where the Ignite 3 component requires to be "enabled" when the cluster configuration is applied. The lifecycle of the component can be adjusted to follow these steps: creating the component, starting the component, waiting for the required cluster configuration, and enabling the component.

One particular example is the REST component, which needs to be configured with basic authentication. There is a time-lapse between cluster initialization and applying the authentication configuration. During this time, the REST API remains unauthenticated, and the cluster endpoints are available to everyone, as mentioned in the IGNITE-18943 ticket. The component needs to be started -> the cluster must be initialized -> basic auth cluster configuration should be applied -> REST is enabled.

Redesign of the Ignite 3 component lifecycle is a part of this issue.

Issue Links

• relates to: IGNITE-19489 Cancel updateDistributedConfigurationActionFuture if the configuration is applied
• links to: GitHub Pull Request #2941