Add node config init and config generate commands (#16479)

Co-authored-by: anton-bobkov <anton-bobkov@ydb.tech>

Author: mregrock

ydb/docs/en/core/reference/ydb-cli/configs.md

@@ -1,59 +1,132 @@
-## Working with configuration
+## Managing  {{ ydb-short-name }} configuration
 
-### Common command flags
+{% note info %}
 
-* `-f, --filename <filename.yaml>` — read input from a file, `-` for STDIN. It can be specified multiple times for commands accepting multiple files (e.g., resolve). The metadata field will determine the file type.
-* `--output-directory <dir>` — dump/resolve files to a directory.
-* `--strip-metadata` — remove the metadata field from the output.
-* `--all` — extend command output to the entire configuration (see advanced configuration).
-* `--allow-unknown-fields` — allow ignoring unknown fields in the configuration.
+Before YDB CLI 2.20.0, the `{{ ydb-cli }} admin cluster config` commands had the following format: `{{ ydb-cli }} admin config`.
 
-```bash
-# Apply the configuration dynconfig.yaml to the cluster
-{{ ydb-cli }} admin config replace -f dynconfig.yaml
-# Check if it is possible to apply the configuration dynconfig.yaml to the cluster (validate all validators, version, and cluster match)
-{{ ydb-cli }} admin config replace -f dynconfig.yaml --dry-run
-# Apply the configuration dynconfig.yaml to the cluster, ignoring version and cluster checks (version and cluster will still be overwritten with correct ones)
-{{ ydb-cli }} admin config replace -f dynconfig.yaml --force
-# Fetch the main cluster configuration
-{{ ydb-cli }} admin config fetch
-# Fetch all current configuration files of the cluster
-{{ ydb-cli }} admin config fetch --all
-# Generate all possible final configurations for dynconfig.yaml
-{{ ydb-cli }} admin config resolve --all -f dynconfig.yaml
-# Generate the final configuration for dynconfig.yaml with labels tenant=/Root/test and canary=true
-{{ ydb-cli }} admin config resolve -f dynconfig.yaml --label tenant=/Root/test --label canary=true
-# Generate the final configuration for dynconfig.yaml for labels from node 1003
-{{ ydb-cli }} admin config resolve -f dynconfig.yaml --node-id 1003
-# Fetch all temporary configurations of the cluster
-{{ ydb-cli }} admin volatile-config fetch --all --output-directory <dir>
-# Fetch the temporary configuration with id 1 from the cluster
-{{ ydb-cli }} admin volatile-config fetch --id 1
-# Apply the temporary configuration volatile.yaml to the cluster
-{{ ydb-cli }} admin volatile-config add -f volatile.yaml
-# Delete temporary configurations with ids 1 and 3 on the cluster
-{{ ydb-cli }} admin volatile-config drop --id 1 --id 3
-# Delete all temporary configurations on the cluster
-{{ ydb-cli }} admin volatile-config drop --all
-```
+{% endnote %}
+
+This section contains commands for managing the {{ ydb-short-name }} [cluster configuration](../../maintenance/manual/config-overview.md).
+
+- Apply the `dynconfig.yaml` configuration to the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config replace -f dynconfig.yaml
+    ```
+
+- Check if it is possible to apply the configuration dynconfig.yaml to the cluster (check all validators, the configuration version in the yaml file must be 1 higher than the cluster configuration version, the cluster name must match):
+
+    ```bash
+    {{ ydb-cli }} admin cluster config replace -f dynconfig.yaml --dry-run
+    ```
+
+- Apply the `dynconfig.yaml` configuration to the cluster, ignoring version and cluster checks (the version and cluster values will be overwritten with correct values):
+
+    ```bash
+    {{ ydb-cli }} admin cluster config replace -f dynconfig.yaml --force
+    ```
+
+- Fetch the main cluster configuration:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config fetch
+    ```
+
+- Generate all possible final configurations for `dynconfig.yaml`:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config resolve --all -f dynconfig.yaml
+    ```
+
+- Generate the final configuration for `dynconfig.yaml` with the `tenant=/Root/test` and `canary=true` labels:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config resolve -f dynconfig.yaml --label tenant=/Root/test --label canary=true
+    ```
+
+- Generate the final configuration for `dynconfig.yaml` for labels from node 100:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config resolve -f dynconfig.yaml --node-id 100
+    ```
+
+- Generate a dynamic configuration file, based on a static configuration on the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin cluster config genereate
+    ```
+
+- Initialize a directory with the configuration, using the path to the configuration file:
+
+    ```bash
+    {{ ydb-cli }} admin node config init --config-dir <path_to_directory> --from-config <path_to_configuration_file>
+    ```
+
+- Initialize a directory with the configuration, using the configuration from the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin node config init --config-dir <path_to_directory> --seed-node <cluster_node_endpoint>
+    ```
+
+## Managing temporary configuration
+
+This section contains commands for managing [temporary configurations](../../maintenance/manual/dynamic-config-volatile-config.md).
+
+- Fetch all temporary configurations from the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin volatile-config fetch --all --output-directory <dir>
+    ```
+
+- Fetch the temporary configuration with id 1 from the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin volatile-config fetch --id 1
+    ```
+
+- Apply the `volatile.yaml` temporary configuration to the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin volatile-config add -f volatile.yaml
+    ```
+
+- Delete temporary configurations with ids 1 and 3 on the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin volatile-config drop --id 1 --id 3
+    ```
+
+- Delete all temporary configurations on the cluster:
+
+    ```bash
+    {{ ydb-cli }} admin volatile-config drop --all
+    ```
+
+## Parameters
+
+* `-f, --filename <filename.yaml>` — read input from a file, `-` for STDIN. For commands that accept multiple files (e.g., resolve), you can specify it multiple times, the file type will be determined by the metadata field
+* `--output-directory <dir>` — dump/resolve files to a directory
+* `--strip-metadata` — remove the metadata field from the output
+* `--all` — extends the output of commands to the entire configuration (see advanced configuration)
+* `--allow-unknown-fields` — allows ignoring unknown fields in the configuration
 
 ## Scenarios
 
 ### Update the main cluster configuration
 
- ```bash
+```bash
 # Fetch the cluster configuration
-{{ ydb-cli }} admin config fetch > dynconfig.yaml
+{{ ydb-cli }} admin cluster config fetch > dynconfig.yaml
 # Edit the configuration with your favorite editor
 vim dynconfig.yaml
 # Apply the configuration dynconfig.yaml to the cluster
-{{ ydb-cli }} admin config replace -f dynconfig.yaml
+{{ ydb-cli }} admin cluster config replace -f dynconfig.yaml
 ```
 
 Similarly, in one line:
 
 ```bash
-{{ ydb-cli }} admin config fetch | yq '.config.actor_system_config.scheduler.resolution = 128' | {{ ydb-cli }} admin config replace -f -
+{{ ydb-cli }} admin cluster config fetch | yq '.config.actor_system_config.scheduler.resolution = 128' | {{ ydb-cli }} admin cluster config replace -f -
 ```
 
 Command output:
@@ -65,7 +138,7 @@ OK
 ### View the configuration for a specific set of labels
 
 ```bash
-{{ ydb-cli }} admin config resolve --remote --label tenant=/Root/db1 --label canary=true
+{{ ydb-cli }} admin cluster config resolve --remote --label tenant=/Root/db1 --label canary=true
 ```
 
 Command output:
@@ -86,7 +159,7 @@ config:
 ### View the configuration for a specific node
 
 ```bash
-{{ ydb-cli }} admin config resolve --remote --node-id <node_id>
+{{ ydb-cli }} admin cluster config resolve --remote --node-id <node_id>
 ```
 
 Command output:
@@ -107,7 +180,7 @@ config:
 ### Save all configurations locally
 
 ```bash
-{{ ydb-cli }} admin config fetch --all --output-directory <configs_dir>
+{{ ydb-cli }} admin cluster config fetch --all --output-directory <configs_dir>
 ls <configs_dir>
 ```
 
@@ -120,7 +193,7 @@ dynconfig.yaml volatile_1.yaml volatile_3.yaml
 ### View all configurations locally
 
 ```bash
-{{ ydb-cli }} admin config fetch --all
+{{ ydb-cli }} admin cluster config fetch --all
 ```
 
 Command output:
@@ -158,7 +231,7 @@ selectors:
 ### View the final configuration for a specific node from the locally saved original configuration
 
 ```bash
-{{ ydb-cli }} admin config resolve -k <configs_dir> --node-id <node_id>
+{{ ydb-cli }} admin cluster config resolve -k <configs_dir> --node-id <node_id>
 ```
 
 Command output:
@@ -174,4 +247,4 @@ config:
     use_auto_config: true
     node_type: COMPUTE
     cpu_count: 4
-```
+```