Skip to content

Fix/quickstart demo flow#75

Open
lakshay-nasa wants to merge 3 commits into
datahub-project:mainfrom
lakshay-nasa:fix/quickstart-demo-flow
Open

Fix/quickstart demo flow#75
lakshay-nasa wants to merge 3 commits into
datahub-project:mainfrom
lakshay-nasa:fix/quickstart-demo-flow

Conversation

@lakshay-nasa

Copy link
Copy Markdown
Collaborator

Summary

  • Auto-generate DataHub token signing keys so fresh installs work with DataHub v1.5.0.6+
  • Add ENGINES_CONFIG to .env.quickstart so the Docker agent reads the mounted config.yaml
  • Use localhost instead of host.docker.internal in quickstart --demo native flow

Test plan

  • Fresh bash quickstart.sh completes without signing key error
  • Agent at http://localhost:8100 shows the demo engine connected after setup
  • analytics-agent quickstart --demo connects to MySQL on all platforms

DataHub v1.5+ requires DATAHUB_TOKEN_SERVICE_SIGNING_KEY and
DATAHUB_TOKEN_SERVICE_SALT to be non-empty. Without them the
system-update container fails on a fresh install. Auto-generate
both with openssl rand if not already set in the environment.
…ted config

The agent defaults to reading config.yaml from ~/.datahub/analytics-agent/
which does not exist inside the container. Without ENGINES_CONFIG pointing
at /app/config.yaml, the bootstrap seeds no engines and the agent starts
with no data source connected.
….internal

The native demo flow runs the agent directly on the host machine, so
MySQL and DataHub GMS are reachable via localhost. Using host.docker.internal
caused DNS resolution failures on some macOS setups and always fails on Linux
where Docker Desktop is not available.
@lakshay-nasa lakshay-nasa requested a review from shirshanka June 5, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant