Skip to content
This repository was archived by the owner on Apr 4, 2026. It is now read-only.

fix: docker compose defauts for optional env vars#91

Merged
christopherwxyz merged 2 commits into
officialunofficial:mainfrom
marthendalnunes:fix/default-docker-compose
Feb 11, 2026
Merged

fix: docker compose defauts for optional env vars#91
christopherwxyz merged 2 commits into
officialunofficial:mainfrom
marthendalnunes:fix/default-docker-compose

Conversation

@marthendalnunes

Copy link
Copy Markdown
Contributor

Description

The current docker compose command is breaking the waypoint container when optional env vars are unset (like the default env), and it emits unnecessary unset-variable warnings.
image

This PR:

  • Uses Compose defaults for optional hub env vars in docker-compose.yml and docker-compose.backfill.yml.
  • Defaults WAYPOINT_HUB__SUBSCRIBE_TO_ALL_SHARDS to true to prevent bool parse failures when unset.
  • Defaults WAYPOINT_HUB__SHARD_INDICES and WAYPOINT_HUB__HEADERS__X_API_KEY to empty values to avoid unset-variable warnings while preserving optional behavior.

Type of change

  • Bug fix (non-breaking change that fixes an issue)

@christopherwxyz
christopherwxyz self-requested a review February 11, 2026 14:31
@christopherwxyz christopherwxyz self-assigned this Feb 11, 2026
Align waypoint-producer env var comments with all other service blocks.
@christopherwxyz
christopherwxyz merged commit c711b8f into officialunofficial:main Feb 11, 2026
4 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants