Releases: gbh-tech/ops
Release list
v1.18.0
v1.17.0
Minor Changes
- 19d50cd: Add application catalog discovery across multiple app directories.
v1.16.1
v1.16.0
Minor Changes
- 4ec9791: Allow
ecs.clusterto include{env}placeholders for per-environment ECS cluster names.
v1.15.0
Minor Changes
-
4c27ab7: Add
gputo deploy config so ECS task definitions emitresourceRequirementstype=GPU.GPU workloads (for example vLLM on EC2 GPU capacity providers) can now reserve GPUs from
deploy.toml/deploy/config.toml:[production] cpu = 4096 memory = 14336 gpu = 1
When
gpu > 0, the container definition includes:"resourceRequirements": [{ "type": "GPU", "value": "1" }]
Omit the field or set
gpu = 0for CPU-only tasks. Requires an EC2 GPU AMI and a GPU capacity provider; Fargate does not support this setting.
Patch Changes
- ef3c10a: style: refactor Go codebase for consistency and clarity
v1.14.0
Minor Changes
-
161e7ab: Fix CLI shorthand flag conflicts that panicked at command initialization
- Move global
--app-configshort flag from-cto-gto avoid clashes with subcommand flags. - Restore
-fshorthand onecs vars --format. - Split
ecs db-proxyinto its own subcommand instead of aport-forwardalias. - Add a regression test that detects persistent/local shorthand conflicts across the command tree.
- Move global
v1.13.0
Minor Changes
-
b6eafa4: Infer
--app-configbasenames and add-cshort flag--app-config servernow resolves toapps/<app>/deploy/server.toml|yaml|yml(ordeploy/server.toml|yaml|ymlin single-repo mode).- Subpaths such as
--app-config worker/serverresolve insidedeploy/worker/. - A clear fatal error is shown when multiple config files with different extensions exist.
-cis now accepted as a short flag for--app-configonecs,build, andpushcommands.
v1.12.0
Minor Changes
-
46bde22: Add support for external Secrets Manager secret references in deploy config secrets.
Per-service deploy configs can now reference a secret that lives OUTSIDE the service's implicit shared/env path using an inline-table entry:
[stage.secrets] DATABASE_URL = "db_url" # existing CLAUDE_API_KEY = { secret = "anthropic/stage", key = "CLAUDE_API_KEY" } # new external
The
secretfield accepts either a bare name (appended to the cluster ARN prefix) or a fullarn:...ARN. Thekeyfield is the JSON key within the Secrets Manager secret and defaults to the env-var name when omitted.This is supported for both
[global.secrets]and[<env>.secrets](runtime ECS secrets only). Build-time secrets (build_secrets) are unchanged and continue to reject external references.The ECS execution role must be granted
secretsmanager:GetSecretValueon the external secret ARN via Terraform for this to work at runtime.
v1.11.2
Patch Changes
- 45ba51e: Remove --no-interactive flag that is not supported by all AWS CLI versions; non-interactive ECS exec works without explicit flag
v1.11.1
Patch Changes
- 8494d6c: Fix ecs run command failing with missing Interactive parameter in AWS ECS execute-command API call