Summary
REGION support appears to be wired into the GitHub Action inputs, but not into the Docker image that the action executes.
We are trying to create LiveKit Cloud Agents in eu-central using the latest deploy-action region support. The workflow passes:
with:
OPERATION: create
REGION: eu-central
However, the agent was still created in us-east.
What I found
The region support commit adds INPUT_REGION handling in action.yml and passes it into the Go code:
https://github.com/livekit/deploy-action/commit/bd6973070a294f546e090e9c02c392c4d5c5b21c
But action.yml still runs:
docker.io/livekit/cloud-agents-github-plugin:v2.12.1
It looks like the published Docker image may not include the region-supporting Go changes, so REGION is accepted by the action but ignored by the container.
I think we're just missing a release as far as I know - let me know if I can help with anything or self serve this, for now I've used a local fork to deploy successfully to `eu-central` but ideally we could stabilise with a real release
Summary
REGIONsupport appears to be wired into the GitHub Action inputs, but not into the Docker image that the action executes.We are trying to create LiveKit Cloud Agents in
eu-centralusing the latest deploy-action region support. The workflow passes: