Cancel
Showing results for 
Search instead for 
Did you mean: 

Where to set environment variables manually in the Developer Cockpit.

Experimenter
Experimenter

As mention in document 

 

"On developer tenants the environment variables must be set manually in the Developer Cockpit. On operator tenants they are set automatically during application."

 

 

After navigating to Developer Cockpit we are  unable to find where to set environment variables.

 

 

 

 

Thanks

raj

3 REPLIES 3
Highlighted

Re: Where to set environment variables manually in the Developer Cockpit.

Legend
Legend
That is not really true, for the developer tenant you have to set the environment variables in the CloudFoundry environment of your deployed backend application e.g. in your manifest file or as `cf env` commands.

I'll file an issue with the MindSphere documentation team.

Re: Where to set environment variables manually in the Developer Cockpit.

Creator
Creator

@dlouzan Is this done the same in the operator tenant? Can the manifest.yml be changed before deployment or will the operator tenant reject it if it's different to the version in the app app that was 'released' from the developer tenant?

Re: Where to set environment variables manually in the Developer Cockpit.

Legend
Legend
I have recently tested the developer - operator tenant cycle with cf template variables and it worked. Take a look at devosp-demo:
https://gitlab.com/mindsphere/devops-demo/blob/master/manifest.yml
https://gitlab.com/mindsphere/devops-demo/#deploy-to-mindsphere

The devopsadmin component in the same project uses a vars-file.yml for the templated values:
https://gitlab.com/mindsphere/devops-demo/tree/master/devops#mindsphere-deployment