Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skip Sentry configuration in Lando environments #159

Merged
merged 2 commits into from
Sep 17, 2024
Merged

Conversation

matt-bernhardt
Copy link
Member

@matt-bernhardt matt-bernhardt commented Sep 17, 2024

Our current Sentry integration with this app results in exceptions being sent to Sentry even when working locally, which causes confusion and counts against our message quota.

This change prevents local development exceptions from being sent to Sentry. Full details are in the commit message.

Developer

Relevant ticket(s):

https://mitlibraries.atlassian.net/browse/pw-106

Stylesheets

  • Any theme or plugin whose stylesheets have changed has had its version
    string incremented.

Secrets

  • All new secrets have been added to Pantheon tiers
  • Relevant secrets have been updated in Github Actions
  • All new secrets documented in README
  • No secrets are affected

Documentation

  • Project documentation has been updated
  • No documentation changes are needed

Accessibility

  • ANDI or Wave has been run in accordance to
    our guide and
    all issues introduced by these changes have been resolved or opened as new
    issues (link to those issues in the Pull Request details above)
  • There are no a11y implications to this change

Stakeholder approval

  • Stakeholder approval has been confirmed
  • Stakeholder approval is not needed

Dependencies

NO dependencies are updated

Code Reviewer

  • The commit message is clear and follows our guidelines
    (not just this pull request message)
  • The changes have been verified
  • The documentation has been updated or is unnecessary
  • New dependencies are appropriate or there were no changes

** Why are these changes being introduced:

We integrate with Sentry provided a given ENV value is defined in
secrets.json, but this can result in local environments sending
exceptions to Sentry - which be quite noisy and undesired.

** Relevant ticket(s):

* https://mitlibraries.atlassian.net/browse/pw-106

** How does this address that need:

This adds an additional check around the Sentry configuration block,
making sure that the PANTHEON_ENVIRONMENT variable is not sent to
"lando" when integrating with Sentry.

** Document any side effects to this change:

None
@JPrevost JPrevost self-assigned this Sep 17, 2024
@matt-bernhardt matt-bernhardt merged commit 1962b29 into master Sep 17, 2024
3 checks passed
@matt-bernhardt matt-bernhardt deleted the pw-106 branch September 17, 2024 21:00
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.

2 participants