cluster: add the ability to manipulate the configuration #506

LeonidVas · 2023-06-22T11:40:27Z

In the scope of the task needs to add the ability to manipulate configuration (show / update) of single instance and cluster (config from etcd) according to https://www.notion.so/tarantool/tt-3-0-fbd40e724dce4a04919d1a35c506a65b

The configuration is imported from the Tarantool implementation. Part of #506

Part of #506

The patch fixes a different list of Python dependencies on macOS. Part of #506

The configuration is imported from the Tarantool implementation. Part of #506

Part of #506

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

The configuration is imported from the Tarantool implementation. Part of #506

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

The patch fixes a different list of Python dependencies on macOS. Part of #506

The configuration is imported from the Tarantool implementation. Part of #506

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

The configuration is imported from the Tarantool implementation. Part of #506

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

The patch unifies a list of Python dependencies for all jobs. Part of #506

The configuration is imported from the Tarantool implementation. Part of #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

The configuration is imported from the Tarantool implementation. Part of #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

The patch unifies a list of Python dependencies for all jobs. Part of #506

The configuration is imported from the Tarantool implementation. Part of #506

@TarantoolBot

* `tt cluster show` to show a configuration. * `tt cluster publish` to publish a configuration. @TarantoolBot document Title: new module - `cluster` The patch introduces a new module `cluster`. The module has two commands: * show - to show a configuration for a cluster or an instance. * publish - to publish a cluster or an instance configuration. The target could be a cluster or an instance configuration. It could be a fully-merged (from all sources) configuration for an application or just a remote configuration part in case of etcd. Usage: * `tt cluster show (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) [--validate]` * The optional `--validate` flag enables validation for a showed configuration. * `tt cluster publish (<APP_NAME> | <APP_NAME:INSTANCE_NAME> | <URI>) file [--force]` * The optional `--force` flag skips validation of uploaded configuration. The `APP_NAME` is a name of an application. The `INSTANCE_NAME` is a name of an instance in the application. The `URI` specifies a etcd connection settings in the following format: `http(s)://[username:password@]host:port[/prefix][?arguments]` * `prefix` - a base path to Tarantool configuration in etcd. Possible arguments: * `name` - a name of an instance in the cluster configuration. * `timeout` - a request timeout in seconds (default 3.0). * `ssl_key_file` - a path to a private SSL key file. * `ssl_cert_file` - a path to an SSL certificate file. * `ssl_ca_file` - a path to a trusted certificate authorities (CA) file. * `ssl_ca_path` - a path to a trusted certificate authorities (CA) directory. * `verify_host` - set off (default true) verification of the certificate’s name against the host. * `verify_peer` - set off (default true) verification of the peer’s SSL certificate. Part of #506

The patch adds a scheduled job [1] that creates or update [2] a pull request every day if a generated code have been changed. 1. https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#onschedule 2. https://github.com/marketplace/actions/create-pull-request Closes #506

LeonidVas added teamE 8sp labels Jun 22, 2023

psergee assigned oleg-jukovec Jul 17, 2023

LeonidVas added 3sp and removed 8sp labels Jul 20, 2023

oleg-jukovec added a commit that referenced this issue Aug 22, 2023

cluster: support a configuration validation

8640c2d

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 22, 2023

cluster: add a configuration validation support

5505048

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 22, 2023

cluster: add a configuration validation support

2eb60c3

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add a configuration validation support

8f8bab6

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

62dc1b2

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

7f70170

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

8e97ed6

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

886b2d0

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

2bd68ec

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

ci: use test/requirements.txt for dependencies

8e5262e

The patch fixes a different list of Python dependencies on macOS. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add a configuration validation support

bff9e26

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 24, 2023

cluster: add tt cluster show command

30f9ede

Part of #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add tt cluster command

0dfef49

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add a configuration validation support

718d190

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add tt cluster command

151ab39

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add tt cluster command

222b3d2

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add tt cluster command

a0213d3

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

ci: use test/requirements.txt for dependencies

e0b8349

The patch fixes a different list of Python dependencies on macOS. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add a configuration validation support

f4d65c6

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 29, 2023

cluster: add tt cluster command

fc666cb

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Closes #506

oleg-jukovec added a commit that referenced this issue Aug 30, 2023

cluster: add tt cluster command

9b8936d

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 30, 2023

cluster: add tt cluster command

181c9a7

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 30, 2023

cluster: add a configuration validation support

11e0cb1

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 30, 2023

cluster: add tt cluster command

a15398a

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

oleg-jukovec added a commit that referenced this issue Aug 30, 2023

cluster: add tt cluster command

d9c034b

* `tt cluster show` to show a configuration. * `tt cluster public` to public a configuration. Part of #506

oleg-jukovec added a commit that referenced this issue Sep 15, 2023

ci: use test/requirements.txt for dependencies

a537dcc

The patch unifies a list of Python dependencies for all jobs. Part of #506

oleg-jukovec added a commit that referenced this issue Sep 15, 2023

cluster: add a configuration validation support

c903b08

The configuration is imported from the Tarantool implementation. Part of #506

oleg-jukovec added a commit that referenced this issue Sep 15, 2023

cluster: add a configuration validation support

3491b2f

The configuration is imported from the Tarantool implementation. Part of #506

psergee closed this as completed in #587 Sep 20, 2023

psergee pushed a commit that referenced this issue Sep 20, 2023

ci: use test/requirements.txt for dependencies

0e5a5af

The patch unifies a list of Python dependencies for all jobs. Part of #506

psergee pushed a commit that referenced this issue Sep 20, 2023

cluster: add a configuration validation support

c4671ec

The configuration is imported from the Tarantool implementation. Part of #506

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

cluster: add the ability to manipulate the configuration #506

cluster: add the ability to manipulate the configuration #506

LeonidVas commented Jun 22, 2023

cluster: add the ability to manipulate the configuration #506

cluster: add the ability to manipulate the configuration #506

Comments

LeonidVas commented Jun 22, 2023