Page MenuHomeSoftware Heritage

Configure vault cookers to send their issue to sentry
AbandonedPublic

Authored by ardumont on Feb 8 2022, 4:18 PM.

Details

Diff Detail

Repository
rSPSITE puppet-swh-site
Branch
staging
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 26677
Build 41716: arc lint + arc unit

Event Timeline

ardumont created this revision.
This revision is now accepted and ready to land.Feb 8 2022, 4:20 PM

Actually no, it's supposed to already do it with [1].

And the setup is actually ok in the parameters.conf.d [3]

[1] https://forge.softwareheritage.org/source/puppet-swh-site/browse/production/site-modules/profile/manifests/swh/deploy/worker/vault_cooker.pp$21
[2] https://forge.softwareheritage.org/source/puppet-swh-site/browse/production/site-modules/profile/manifests/swh/deploy/worker/instance.pp$36-38

[3]

ardumont@worker12:~% grep -i sentry /etc/systemd/system/swh-worker@vault_cooker.service.d/parameters.conf
Environment=SWH_SENTRY_DSN=https://<redacted>@sentry.softwareheritage.org/11
Environment=SWH_SENTRY_ENVIRONMENT=production

If there is something to do here, it's to drop the sentry_swh_package and sentry_environment which are unused (lines 276{3-4})