Skip to content

Releases: gbh-tech/ops

v1.18.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 09 Sep 00:55
50e5ffa

Minor Changes

  • 1360282: Add configurable ECS registry repository paths with {env} and {service} placeholders.

v1.17.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 07 Sep 13:50
6c19e62

Minor Changes

  • 19d50cd: Add application catalog discovery across multiple app directories.

v1.16.1

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 25 Aug 19:05
fd18828

Patch Changes

  • 0428a4e: Allow explicit ECS database migrations to run for apps configured with zero replicas.
  • 0327187: Cause the command to fail when ECS migration task results are unsuccessful or indeterminate.

v1.16.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 15 Jul 20:04
142e44a

Minor Changes

  • 4ec9791: Allow ecs.cluster to include {env} placeholders for per-environment ECS cluster names.

v1.15.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 10 Jul 00:43
243b413

Minor Changes

  • 4c27ab7: Add gpu to deploy config so ECS task definitions emit resourceRequirements type=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 = 0 for 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

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 03 Jul 23:11
5759442

Minor Changes

  • 161e7ab: Fix CLI shorthand flag conflicts that panicked at command initialization

    • Move global --app-config short flag from -c to -g to avoid clashes with subcommand flags.
    • Restore -f shorthand on ecs vars --format.
    • Split ecs db-proxy into its own subcommand instead of a port-forward alias.
    • Add a regression test that detects persistent/local shorthand conflicts across the command tree.

v1.13.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 02 Jul 17:48
95e5140

Minor Changes

  • b6eafa4: Infer --app-config basenames and add -c short flag

    • --app-config server now resolves to apps/<app>/deploy/server.toml|yaml|yml (or deploy/server.toml|yaml|yml in single-repo mode).
    • Subpaths such as --app-config worker/server resolve inside deploy/worker/.
    • A clear fatal error is shown when multiple config files with different extensions exist.
    • -c is now accepted as a short flag for --app-config on ecs, build, and push commands.

v1.12.0

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 15 Jun 23:31
4d1be04

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 secret field accepts either a bare name (appended to the cluster ARN prefix) or a full arn:... ARN. The key field 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:GetSecretValue on the external secret ARN via Terraform for this to work at runtime.

v1.11.2

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 12 Jun 18:52
02c2d9c

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

Choose a tag to compare

@gbh-devops-bot gbh-devops-bot released this 12 Jun 12:58
f562cf4

Patch Changes

  • 8494d6c: Fix ecs run command failing with missing Interactive parameter in AWS ECS execute-command API call