blocks
top-level element
Attributes
module
The module
attribute refers to a Nullstone module that is registered in the Nullstone registry.
- In
.nullstone/config.yml
,module
is required for every defined application. - In overrides files,
module
is optional and alters the chosen module.
The vars
and connections
schema is loaded from the chosen module
. Validation is performed using this schema in the vars
and connections
section.
module_version
The module_version
attribute allows selection of a specific published version to the module registry. If this value is not specified, module_version
will default to "latest"
. Nullstone will look up the latest published version of the module in the registry based on semver.
When the effective module version changes, the module schema is pulled from the registry to validate vars
and connections
.
vars
The vars
section is used to provide configuration for this block. The available variables are based on the selected module
/module_version
. To view a list of available variables for a module version, visit the "Inputs" tab for a module version in the registry. (Example: nullstone/aws-network@0.7.8)
If a variable does not have a default value defined in the registry, the variable must be specified. This value can be specified in either .nullstone/config.yml
or and overrides file.
connections
The connections
section is used to connect one block to another block. Connections enable a block gain contextual information about another block.
For example, a container app is provisioned on a cluster namespace. Therefore, the container app has a connection named cluster-namespace
where a user can identify which namespace to provision. This connection value refers to another Nullstone block that is a compatible cluster namespace for the container app.