Expose Sentry related env var in dashboard pod

[lbarcziova]

Related to packit/dashboard#410

[lbarcziova]

I see the PR actually requires 2 env vars, I will have a look into the SENTRY_AUTH_TOKEN.

[softwarefactory-project-zuul]

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/b986d85493a34a658a6511719b575532

✔️ pre-commit SUCCESS in 1m 51s
❌ deployment-tests RETRY_LIMIT in 7m 19s

[mfocko]

Why isn't DSN enough? 👀

[Venefilyn]

Why isn't DSN enough? 👀

@mfocko SENTRY_AUTH_TOKEN is to provide sourcemaps to Sentry so that it can decipher production builds, as they are minimized

[mfocko]

Correct me if I'm wrong, but based on the docs:

• https://www.npmjs.com/package/@sentry/vite-plugin#authtoken
• https://docs.sentry.io/platforms/javascript/guides/gcp-functions/sourcemaps/uploading/vite/#configuration

I understand that this token needs to be present during the build, not while deployed, so this is something that should be exposed in the dashboard repo and for the GH Action (that actually builds the images).

Based on the docs from the first link, I have a feeling that it should work correctly by matching the commit SHA to the image.

I'm not very happy about having the org-wide Sentry token present in the deployment, if (hopefully) there's no need for it.

(Based on the discussion with @lbarcziova)

[Venefilyn]

I understand that this token needs to be present during the build, not while deployed

Correct, should only be needed during build

[lbarcziova]

thanks @Venefilyn for confirmation! Then I updated this PR only adding the VITE_SENTRY_DSN and the SENTRY_AUTH_TOKEN will be added in the dashboard repo.

[softwarefactory-project-zuul]

Build failed.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/b316dca32f1b4548ae9650390e2e2ef1

✔️ pre-commit SUCCESS in 1m 42s
❌ deployment-tests RETRY_LIMIT in 7m 16s