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

OPE-10714 Use SENTRY_ENVIRONMENT instead of NODE_ENV to set Sentry Environment #37

Merged
merged 2 commits into from
Jun 23, 2020

Conversation

Farzy
Copy link
Contributor

@Farzy Farzy commented Jun 23, 2020

Using NODE_ENV was a mistake from the start. NODE_ENV should only be used to configure NodeJS.

SENTRY_ENVIRONMENT lets use configure different environments in Sentry using the same DSN.

…vironment

Using NODE_ENV was a mistake from the start.
@Farzy Farzy requested a review from a team June 23, 2020 12:24
@codecov
Copy link

codecov bot commented Jun 23, 2020

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##            master       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           39        39           
=========================================
  Hits            39        39           
Impacted Files Coverage Δ
index.js 100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8e217c1...3f902a2. Read the comment docs.

Copy link

@Kenny407 Kenny407 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌 thanks Farzad !

Copy link
Contributor

@Antoninbln Antoninbln left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you update the version defined in package.json, and define the release here please ?
Then we'll be able to publish the package update :)
Otherwise it LGTM 👍

@Farzy Farzy merged commit f2ab187 into master Jun 23, 2020
@Farzy Farzy deleted the OPE-10714 branch June 23, 2020 12:42
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.

3 participants