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

feat: add support for env name from auth #410

Merged
merged 2 commits into from
Feb 24, 2022
Merged

Conversation

JamieDanielson
Copy link
Contributor

@JamieDanielson JamieDanielson commented Feb 23, 2022

Which problem is this PR solving?

Short description of the changes

  • Environment name will be returned in auth call in addition to slug.
  • Environment slug is no longer supported in the rules file. If it becomes an issue and there is high demand for it, we can consider adding it as an option later.
  • Using the environment name instead of the slug is more intuitive for end users, as they set the environment name intentionally, not the slug. This can now be used in the rules config instead of worrying about the structure of the slugified version of the environment.

route/route.go Outdated Show resolved Hide resolved
@JamieDanielson JamieDanielson changed the title WIP: add support for env name from auth feat: add support for env name from auth Feb 23, 2022
@JamieDanielson JamieDanielson self-assigned this Feb 23, 2022
@JamieDanielson JamieDanielson added type: enhancement New feature or request version: bump minor A PR that adds behavior, but is backwards-compatible. version: bump major A PR that breaks backwards compatibility. labels Feb 23, 2022
@MikeGoldsmith
Copy link
Contributor

Yeah, this looks good and is what I expected. We don't need to support both env. slug and name as no one is able to use new v2 keys yet.

@JamieDanielson JamieDanielson marked this pull request as ready for review February 24, 2022 19:04
@JamieDanielson JamieDanielson requested a review from a team February 24, 2022 19:04
@JamieDanielson
Copy link
Contributor Author

Will create a follow-up issue to make it clear that this is the supported version for E&S, not the previous version that used slugs.

@JamieDanielson JamieDanielson merged commit 6932877 into main Feb 24, 2022
@JamieDanielson JamieDanielson deleted the jamie.env-name branch February 24, 2022 19:06
ghost pushed a commit to opsramp/tracing-proxy that referenced this pull request Jul 5, 2024
* add support for env name from auth
* use only env name in auth call and cache

closes [Support non-slugified environment names](honeycombio#407) honeycombio#407
* Environment name will be returned in auth call in addition to slug.
* Environment slug is no longer supported in the rules file. If it becomes an issue and there is high demand for it, we can consider adding it as an option later.
* Using the environment name instead of the slug is more intuitive for end users, as they set the environment name intentionally, not the slug. This can now be used in the rules config instead of worrying about the structure of the slugified version of the environment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request version: bump major A PR that breaks backwards compatibility. version: bump minor A PR that adds behavior, but is backwards-compatible.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support non-slugified environment names
3 participants