There are two layouts, one for private environments and one for public environments.
Prerequisites:
Add to run config should not use environment id, instead, it should do the following:
For local deployments, add an env variable for the values: 'digma.environment' : For example, OTEL_RESOURCE_ATTRIBUTES=digma.environment=[ENVIRONMENT_NAME]
For centralized deployment, add an en variable for the values: digma.environment, digma.environment.type, digma.user.id. For example: OTEL_RESOURCE_ATTRIBUTES=digma.environment=[ENVIRONMENT_NAME],digma.environment.type=[ENVIRONMENT_TYPE],digma.user.id=[USERID]
On the left panel, we need to change the env variable example to be the same as what we do today with "Set active run config"
If the environment is already or was just set by the user for the current run config, instead of the button we show an indicator that the environment is active and a link to remove it.
doppleware
commented
4 months ago
There are two layouts, one for private environments and one for public environments.
Prerequisites: Add to run config should not use environment id, instead, it should do the following:
OTEL_RESOURCE_ATTRIBUTES=digma.environment=[ENVIRONMENT_NAME]digma.environment,digma.environment.type,digma.user.id. For example:OTEL_RESOURCE_ATTRIBUTES=digma.environment=[ENVIRONMENT_NAME],digma.environment.type=[ENVIRONMENT_TYPE],digma.user.id=[USERID]Private environment layout here:
https://www.figma.com/design/MxA95ZHK5NqGX4ptFQljRJ/%E2%AD%90-Design-System-3.0?node-id=7694-114747&t=x5cWZ0UdPEsY0AO3-4
On the left panel, we need to change the env variable example to be the same as what we do today with "Set active run config"
If the environment is already or was just set by the user for the current run config, instead of the button we show an indicator that the environment is active and a link to remove it.
Public environment layout here:
https://www.figma.com/design/MxA95ZHK5NqGX4ptFQljRJ/%E2%AD%90-Design-System-3.0?node-id=7708-114876&t=x5cWZ0UdPEsY0AO3-4