Reusable templates for your services
ryvn.yaml
file. See the infrastructure as code
guide to learn how to configure ryvn.yaml
syncing before using blueprints.
Here is an example of a blueprint of a simple application consisting of a frontend and backend web-server.
Type | Description | Example |
---|---|---|
string | Text values | Application names, URLs |
number | Numeric values | CPU cores, memory limits |
boolean | True/false values | Feature flags, enable/disable options |
array | Lists of values | Port lists, environment names |
object | Complex data structures | Configuration objects |
Property | Description | Required |
---|---|---|
name | Unique identifier for the input | Yes |
type | Data type (string, number, boolean, array, object) | Yes |
description | Detailed explanation of the input’s purpose | No |
displayName | Human-readable name for the UI | No |
default | Default value if not specified | No |
config
field contains service-specific configuration as a YAML string. This is the same configuration that you would
provide to the service when installing it manually. For helm charts, this is the same as the override values.yaml
file and for
terraform, this is the same as the variables yaml file.
Type | Description | Use Case |
---|---|---|
random-string | Random alphanumeric string | API keys, tokens |
random-bytes | Random binary data | Encryption keys |
rsa-key | RSA key pair | SSL certificates, SSH keys |
ec-key | Elliptic curve key pair | Modern cryptography |
Option | Description | Required |
---|---|---|
blueprint | Name of the blueprint to install | Yes |
name | Custom name for this installation | No |
inputs | Values for blueprint inputs | No |
name
for each installation.