Hi All,
We were checking whether there was any possibility of having access to your UI or BIZ solution for the type of environment in which we are currently running our solution.
This means accessing this value:
After an internal investigation and conversation with my colleague, we were able to find some limitations and a possible solution that we would like to confirm before proceeding to do it.
1º:
Via DEE and by throwing all enviroment variables, we were able to see that, on the host by default, there is no “ENVIRONMENT_TYPE” variable
2º
We noticed that the service that provides information to the DEVOPSCenter is this one, and it is not accessible in our UI or Biz by default:
3º
This ENVIRONMENT_TYPE is available in the Traefik pod already:
Taking this information into consideration, we think that the solution for this should be adding a new Enviroment variable to the host deployment:
Please let us know your reply.
Best Regards,
João Querido
Hi @Joao_Querido,
After reviewing this with you earlier, it seems that this is the best solution to retrieve the environment type. You can add any needed Environment Variables there as long as they don’t collide with existing ones for the same resource. Being this, my only suggestion would be to name the key something that would not collide in the future. The ENVIRONMENT_TYPE key is already used by MES deployment, and in case it’s needed for the host for some reason, you could be overwriting its value.
So my suggestion would be to name it CUSTOM_ENVIRONMENT_TYPE or ClientName_ENVIRONMENT_TYPE, anything that by being specific would have less chance of collision in the future.
Hope this helps. 
Hi João,
Based on your description, it seems that the best solution is the one Filipe pointed out.
My reply to this topic is mainly to understand the scenario or use case where you need this discrimination, because I can see some benefit in having this environment variable automatically set on the Host deployment out of the box (enhancement request). For example, for environment-specific configuration or connection settings to external systems, which usually differ between development, QA, and production environments. These settings need to be carefully managed throughout the lifecycle to avoid potential conflicts, such as “Move Environment” operations from Production to other environment types, which are very common after the Production environment has been live for some time and new project phases are implemented and tested against a similar copy).
Ricardo
