When creating a render.yaml file with a envVarGroups option with multiple keys that all have sync: false. There is no option during the build process where these can be added before all the services are built etc. Image below shows the Environment Group setup I currently have where none of these are prompted for when adding this YAML to the render interface. Not sure why this is the case considering the example YAML shows that you can use the sync: false functionality.
If this is an automated build or sync, you wonât have an opportunity to fill those values. But, if youâre creating a new set of services via âNew from YAMLâ
you should be prompted to enter in values for those environment variables.
That is the issue unfortunately. There was no prompt at all when importing the YAML file to add those variable values and so the build fails. I will try again today but I never got any text fields when the YAML file was added despite having sync false on all variables in the group
Ah, youâre right. It doesnât work for environment groups. Letâs see if we can get that supported.
+1 for this please. Also, environment groups with variables as sync: false donât even get created for me.
The ideal scenario would be for them to work exactly the same as sync: false variables in services. Just ask for the value on deploy.
Iâm having to do this ugly thing:
And then after deploy I have to remember to go and set that.
I have to do it this way because this value is used by multiple services in the blueprint and is a JWT secret in the format: {"type":"HS256","key":"OrgDWKuSbPEIAARaaRAQQcjCmJePU8rdslkjURocpVlaLCttcMqjIBIYCC6MwT1JMDo3yiOJpIGvjd"} and I canât generate that format randomly on the fly. If there was some sort of string interpolation syntax for blueprints then I could⌠Which would be great
Please. Thanks
Yep, we hear you! Weâre working to improve this area for sure!
+1, having the prompt for envVarGroups would be great!
EDIT: Actually, this is weird because it seems to work if the env group is updated. If you create it before setting up the blueprint, youâll have the input prompts. However, if itâs not created, the inputs are not showed.
Creation :
