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.

Sign up for GitHub

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

Jump to bottom

Be explicit with env tags #3

Open
burningion opened this issue Feb 19, 2020 · 1 comment
Open

Be explicit with env tags #3

burningion opened this issue Feb 19, 2020 · 1 comment

Comments

@burningion
Copy link
Contributor

A few people have noted different env settings depending on the service. The env tag is explicitly set in the Ruby service, but not the downstream Python services.

Let's make sure every service has an explicitly set environment, so we have consistent services.
@stevedatadog
Copy link
Collaborator

Since #150 we have standardized on the default development. Should we close this, @burningion ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@burningion @stevedatadog