semvec/pypi-packages huggingface dataset:
th2-cli 1.7.3
👨‍💻 CLI for managing th2 infrastructure in Kubernetes cluster
License: MIT
Requires Python: >=3.8,<4.0
Keywords: th2,cli,kubernetes,cassandra,helm-charts

Works with th2 1.7.3

## Using

Install:

```commandline
pip install th2-cli
```

Check version of CLI:

```commandline
th2 version
```

Output example:

```commandline
$ th2 version
th2 CLI v1.7.3
Source repository: https://github.com/d0rich/th2-cli
```

### Install th2

If you already have configurations in `th2-cli-install-config.yaml` or `secrets.yaml`, it will be convenient to run process from the directory with these files.
In other case CLI will create these config files during installation.

```commandline
th2 install
```

### Delete th2

```commandline
th2 delete
```

### Update th2

```commandline
th2 delete
```

Wait until all required namespaces are terminated.

```commandline
th2 install
```

### Get th2 status

Display information about all th2-related namespaces in Kubernetes.

```commandline
th2 status
```

### infra-mgr

Display status of infra-mgr pod:

```commandline
th2 mgr status
```

Display last logs of infra-mgr pod:

```commandline
th2 mgr logs
```

## Configurations templates

### th2-cli-install-config.yaml

```yaml
cassandra:
  datacenter: datacenter1
  host: host.minikube.internal
infra-mgr:
  git:
    http-auth-password: pat_token
    http-auth-username: pat_token
    repository: https://github.com/schema/repository
kubernetes:
  host: 192.168.49.2
  pvs-node: minikube
```

### secrets.yaml

```yaml
# required only for images from a private registry, will be attached as the first PullSecret to deployments
#productRegistry:
#  username: user
#  password: password
#  name: private-registry-1.example.com # core components registry

# required only for images from a private registry, will be attached as the second PullSecret to deployments
#solutionRegistry:
#  username: user
#  password: password
#  name: private-registry-2.example.com # components registry

# required only for images from a private registry, will be attached as the third PullSecret to deployments
#proprietaryRegistry:
#  username: user
#  password: password
#  name: private-registry-3.example.com # components registry

cassandra:
# set credentials for the existing Cassandra cluster
  dbUser:
    user: cassandra
    password: cassandra

rabbitmq:
# set admin user credentials, it will be created during deployment
  rabbitmqUsername: th2
  rabbitmqPassword: rab-pass
  # must be random string
  rabbitmqErlangCookie: cookie
```

## Development

```
poetry install
poetry shell
```

```commandline
th2 install
```