getting-started/telemetry example does not work #1871
Description
Describe the bug
When testing 1.0.x, I encountered that the polaris-setup container fails when starting the telemetry example, resulting in the example catalog to not be created.
It seems the CLIENT_ID and CLIENT_SECRET env variables are never set in the getting-started/telemetry/docker-compose.yml, causing the create-catalog.sh script within polaris-setup container to fail with the following logs:
fetch [https://dl-cdn.alpinelinux.org/alpine/v3.21/main/aarch64/APKINDEX.tar.gz](https://dl-cdn.alpinelinux.org/alpine/v3.21/main/aarch64/APKINDEX.tar.gz)
fetch [https://dl-cdn.alpinelinux.org/alpine/v3.21/community/aarch64/APKINDEX.tar.gz](https://dl-cdn.alpinelinux.org/alpine/v3.21/community/aarch64/APKINDEX.tar.gz)
(1/2) Installing oniguruma (6.9.9-r0)
(2/2) Installing jq (1.7.1-r0)
Executing busybox-1.37.0-r12.trigger
OK: 13 MiB in 26 packages
Failed to obtain access token.
Additionally, the parameter that is passed in within this README command should be corrected to match the new catalog name of quickstart_polaris instead of polaris_demo.
To Reproduce
No response
Actual Behavior
No response
Expected Behavior
No response
Additional context
No response
System information
No response