ize.toml
1.1.4Schema URL
Properties
(optional) AWS Profile can be specified here (but normally it's specified via AWS_PROFILE env var)
(required) AWS Region of this environment should be specified here. Can be overridden by AWS_PROFILE env var or --aws-region flag.
(optional) Environment name can be specified here. Normally it should be passed via ENV variable or --env flag.
(optional) Environment directory can be specified here. Normally it's calculated automatically based on the directory structure convention.
(optional) User home directory can be specified here. Normally $HOME is used.
(optional) Ize directory can be specified here. Normally it's assumed to be .infra or .ize in the current repo.
(required) Namespace of the project can be specified here. It is used as a base for all naming. It can be overridden by NAMESPACE env var or --namespace flag.
(optional) Prefer a specific runtime. (native or docker) (default 'native')
(optional) Project directory can be set here. By default it's the current directory, but in case you prefer to run ize from the outside of repo it may be useful (uncommon).
(optional) Path to ize.toml config file can be specified, but normally it's read from the environment's directory automatically.
(optional) Log level can be specified here. Possible levels: info, debug, trace, panic, warn, error, fatal(default). Can be overridden via IZE_LOG_LEVEL env var or via --log-level flag.
(optional) Plain text output can be enabled here. Default is false. Can be overridden by IZE_PLAIN_TEXT env var or --plain-text flag.
(optional) Path to apps directory can be set. By default apps are searched in 'apps' and 'projects' directories. This is needed in case your repo structure is not purely ize-structured (let's say you have 'src' repo in your dotnet app, as an example)
(optional) Terraform version can be set here. 1.1.3 by default
(optional) Docker registry can be set here. By default it uses ECR repo with the name of the service.
(optional) TF_LOG_PATH can be set here.
(optional) Tag can be set statically. Normally it is being constructed automatically based on the git revision.
(optional) Terraform TF_LOG can be set here. Can be TRACE, DEBUG, INFO, WARN or ERROR.
(optional) Custom prompt can be enabled here for all console connections. Default: false.
Tunnel configuration.
2 nested properties
Bastion instance ID.
Apps configuration.
Ecs apps configuration.
Serverless apps configuration.
(optional) Alias mode can be enabled here. This can be used to combine various apps via depends_on parameter.
Terraform configuration.
Infrastructure configuration.
2 nested properties
Infrastructure configuration.
7 nested properties
(optional) Terraform version can be set here. 1.1.3 by default.
(optional) Terraform state bucket region can be specified here. Normally AWS_REGION is used here. Can be overridden via env vars or flags.
(optional) Terraform state bucket name can be specified here. Normally it's generated and defaults to
(optional) Root domain name can be set here. This is the main domain that will be passed to the terraform. Generally if your app lives at 'api.dev.nutcorp.net' the root domain is nutcorp.net
(optional) Terraform-specific AWS Region of this environment should be specified here. Normally global AWS_REGION is used.
(optional) Terraform-specific AWS profile (optional) can be specified here (but normally it should be inherited from a global AWS_PROFILE).
Tunnel configuration.
2 nested properties
Bastion instance ID.
Definitions
App configuration.
app type
(optional) Path to serverless file can be specified here. Normally it's serverless.yml in the app directory.
(optional) Node version that will be used by nvm can be specified here that. Default is v14.
(optional) Create domain for the serverless domain manager during the deployment.
(optional) Path to ecs app folder can be specified here. By default it's derived from apps path and app name.
(optional) SLS node_modules cache mount path can be specified here. It's used to store cache during CI/CD process.
environments
(optional) Enables unsafe mode that increases deploy time on a cost of shorter healthcheck.
(optional) Docker image can be specified here. By default it's derived from the app name.
(optional) ECS cluster can be specified here. By default it's derived from env & namespace
(optional) Task definition revision can be specified here. By default latest revision is used to perform a deployment. Normally this parameter can be used via cli during specific deployment needs.
(optional) ECS deployment timeout can be specified here.
(optional) Docker registry can be set here. By default it uses ECR repo with the name of the service.
(optional) skip deploy app.
(optional) expresses startup and shutdown dependencies between apps
Ecs app configuration.
(optional) Path to ecs app folder can be specified here. By default it's derived from apps path and app name.
(optional) Enables unsafe mode that increases deploy time on a cost of shorter healthcheck.
(optional) Docker image can be specified here. By default it's derived from the app name.
(optional) ECS cluster can be specified here. By default it's derived from env & namespace
(optional) Task definition revision can be specified here. By default latest revision is used to perform a deployment. Normally this parameter can be used via cli during specific deployment needs.
(optional) ECS deployment timeout can be specified here.
(optional) Docker registry can be set here. By default it uses ECR repo with the name of the service.
(optional) skip deploy app.
(optional) set icon
(optional) ECS-specific AWS Region of this environment should be specified here. Normally global AWS_REGION is used.
(optional) ECS-specific AWS profile (optional) can be specified here (but normally it should be inherited from a global AWS_PROFILE).
(optional) expresses startup and shutdown dependencies between apps
Serverless app configuration.
(optional) Path to serverless file can be specified here. Normally it's serverless.yml in the app directory.
(optional) Node version that will be used by nvm can be specified here that. Default is v14.
(optional) Create domain for the serverless domain manager during the deployment.
(optional) Path to the serverless app directory can be specified here. Normally it's derived from app directory and app name.
(optional) SLS node_modules cache mount path can be specified here. It's used to store cache during CI/CD process.
environments
(optional) set icon
(optional) Serverless-specific AWS Region of this environment should be specified here. Normally global AWS_REGION is used.
(optional) Serverless-specific AWS profile (optional) can be specified here (but normally it should be inherited from a global AWS_PROFILE).
(optional) expresses startup and shutdown dependencies between apps
Alias configuration.
(optional) set icon
(optional) expresses startup and shutdown dependencies between apps
Terraform configuration
(optional) Terraform version can be set here. 1.1.3 by default.
(optional) Terraform state bucket region can be specified here. Normally AWS_REGION is used here. Can be overridden via env vars or flags.
(optional) Terraform state bucket name can be specified here. Normally it's generated and defaults to
(optional) Root domain name can be set here. This is the main domain that will be passed to the terraform. Generally if your app lives at 'api.dev.nutcorp.net' the root domain is nutcorp.net
(optional) Terraform-specific AWS Region of this environment should be specified here. Normally global AWS_REGION is used.
(optional) Terraform-specific AWS profile (optional) can be specified here (but normally it should be inherited from a global AWS_PROFILE).