Implementing solution for 'env deprecated' warning, encountering unexpected behavior with platform_instance usage

Original Slack Thread

Good Morning Community - we are trying to implement the suggested solution for the below warning:

['env is deprecated and will be removed in a future release. Please use platform_instance instead.']```
but running into some wierd behaviour when we use platform_instance instead of "env" config. In TRINO source for example, we removed "env" param and instead set the platform_instance to "DEV". However, the datasets created were of urn format: <http://DEV.DEV|DEV.DEV>.<schema>.dataset,PROD. We understand that the default valuefor "env" is PROD, so we see the TRINO datasets under the PROD env while navigating from the homepage. Also we dont understand why there is an addition DEV layer created after the platform_instance DEV (*<http://DEV.DEV|DEV.DEV>*...) ?
We dont want to see PROD env in our datahub test environment instance but if we dont set "env" config in recipe, by default all datasets are being created under PROD env. How can this be resolved?
Also if someone can look into why the additional DEV layer got created under the platform_instance.
In our another use case, we have a HIVE platform which already has 2 platform instances X and Y, in that case we will not be able to use this platform_instance config for setting the env DEV or PROD.
Please advise.
<@U03BEML16LB> <@UV14447EU> <@U01GZEETMEZ> <@UV14447EU>

Hey there! :wave: Make sure your message includes the following information if relevant, so we can help more effectively!

  1. Which DataHub version are you using? (e.g. 0.12.0)
  2. Please post any relevant error logs on the thread!