Apply

rio apply

Apply resource manifests.

The apply command provides the mechanism to create or update resources on rapyuta.io. The resources are defined in YAML manifests allowing for a declarative and repeatable process. The command can take multiple files, paths or globs as arguments and parse the manifests to create or update resources. It also supports Jinja templating and secret management with sops.

You can provide value files with the --values option and sops encrypted secret files with --secret option.

You can use the --show-graph option to visualize the dependency graph of the resources defined in the manifests.

The –dryrun option can be used to execute the manifests without actually creating the resources. This is useful to validate the manifests before applying them.

You can specify the number of parallel workers with the --workers option. The default value is 6.

The --silent, --force or -f option lets you skip the confirmation prompt before applying the manifests. This is particularly useful in CI/CD pipelines.

Usage Examples:

Apply a single manifest file with secret and values file.

$ rio apply -v values.yaml -s secrets.yaml manifest.yaml

Apply manifests from a directory with secret and values file.

$ rio apply -v values.yaml -s secrets.yaml templates/

Apply manifests from a directory without confirmation prompt.

$ rio apply -f templates/

Apply manifests with multiple value files.

$ rio apply -v values1.yaml -v values2.yaml templates/**

rio apply [OPTIONS] [FILES]...

Options

-d, --dryrun

Dry run the yaml files without applying any change

-g, --show-graph

Opens a mermaid.live dependency graph

-v, --values <values>

Path to values yaml file. Key/values specified in the values file can be used as variables in template YAMLs

-s, --secrets <secrets>

Secret files are sops encoded value files. rio-cli expects sops to be authorized for decoding files on this computer

-w, --workers <workers>

Number of parallel workers while running apply command. defaults to 6.

-f, --force, --silent

Skip confirmation

-rc, --retry-count <retry_count>

Number of retries before a resource creation times out status, defaults to 50

-ri, --retry-interval <retry_interval>

Interval between retries defaults to 6

Arguments

FILES

Optional argument(s)

rio delete

Removes resources via manifests

The delete command provides the mechanism to remove resources on rapyuta.io defined in YAML manifests making the process declarative and repeatable. The command can take multiple files, paths or globs as arguments and parse the manifests to remove resources. It also supports Jinja templating and secret management with sops.

You can provide value files with the --values option and sops encrypted secret files with --secret option.

The --dryrun option can be used to execute the manifests without actually deleting the resources. This is useful to validate the manifests before applying them.

You can specify the number of parallel workers with the --workers option. The default value is 6.

The --silent, --force or -f option lets you skip the confirmation prompt before applying the manifests. This is particularly useful in CI/CD pipelines.

Usage Examples:

Delete a single manifest file with secret and values file.

$ rio delete -v values.yaml -s secrets.yaml manifest.yaml

Delete manifests from a directory with secret and values file.

$ rio delete -v values.yaml -s secrets.yaml templates/

Delete manifests from a directory without confirmation prompt.

$ rio delete -f templates/

Delete manifests with multiple value files.

$ rio delete -v values1.yaml -v values2.yaml templates/**

rio delete [OPTIONS] [FILES]...

Options

-d, --dryrun

Dry run the yaml files without applying any change

-v, --values <values>

Path to values yaml file. key/values specified in the values file can be used as variables in template YAMLs

-s, --secrets <secrets>

Secret files are sops encoded value files. riocli expects sops to be authorized for decoding files on this computer

-f, --force, --silent

Skip confirmation

-w, --workers <workers>

Number of parallel workers while running apply command. defaults to 6.

-rc, --retry-count <retry_count>

Number of retries before a resource creation times out status, defaults to 50

-ri, --retry-interval <retry_interval>

Interval between retries defaults to 6

Arguments

FILES

Optional argument(s)