-
Notifications
You must be signed in to change notification settings - Fork 175
Open
Labels
Description
Checklist
- I have looked into the README and have not found a suitable solution or answer.
- I have looked into the documentation and have not found a suitable solution or answer.
- I have searched the issues and have not found a suitable solution or answer.
- I have upgraded to the latest version of this tool and the issue still persists.
- I have searched the Auth0 Community forums and have not found a suitable solution or answer.
- I agree to the terms within the Auth0 Code of Conduct.
Description
Summary
a0deploy import hangs on Linux CI runner at:
Getting access token for <tenant-domain>
Versions tested
- ✅ Works: auth0-deploy-cli 8.16.0
- ❌ Hangs: 8.22.0, 8.28.0
Environment
- Runner: self-hosted Linux (EKS)
- Node: 22.22.0
- npm:
- Command:
a0deploy import --env=true --input_file ./src --config_file ./config/config.json --prune --allow-delete
Expected
Import continues and completes.
Actual
Command hangs indefinitely after “Getting access token…”.
Logs (sanitized)
What we validated
- TLS/SNI connectivity from runner works via Node HTTPS and curl.
- Auth0 tenant/domain reachable.
- Secrets/env values present.
Mitigations attempted
- Pre-generate token via
/oauth/tokenand passAUTH0_ACCESS_TOKEN - Unset client credentials and force token path
- Added workflow debug for env/config propagation
- Still hangs in affected versions
Workaround
Pinning to auth0-deploy-cli@8.16.0 resolves deployment on same runner.
Reproducibility
- Reproducible on our CI runner: always
- Local Windows: does not reproduce
Expectation
auth0-deploy-cli import should complete successfully on Linux GitHub Actions runners (same tenant/config as local), obtain auth without hanging, and proceed to deploy all configured assets i
Reproduction
Deploy CLI version
8.28.0
Node version
22.22.0
Reactions are currently unavailable