Teams organize their testing on various projects. Projects might have different members, scopes, and ways of testing. Projects provide the context for different purposes.
Users could create environment variables at either the Stack/organization or project level. The environment variable at the lowest level takes precedence:
Stack/Organization --> Project --> Passing to the CLI
This is a common pattern in other products such as GitHub.
This issue has been migrated to Grafana Feature requests (please contact support or your account team to submit additional ideas or to add to this one)
Feature description
Teams organize their testing on various projects. Projects might have different members, scopes, and ways of testing. Projects provide the context for different purposes.
This feature requests to allow configuring Environment variables per project. , which is similar to the request: Notifications per project.
Users could create environment variables at either the Stack/organization or project level. The environment variable at the lowest level takes precedence:
This is a common pattern in other products such as GitHub.