-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Environment variables naming #616
Comments
Hello @rvvincelli , please check this issue #579 and tell me if it helps. |
Makes sense. We'l include it in one the following releases. Meantime please use the workaround from the previous post. |
That's a very good point - thanks!! |
wajda
added a commit
that referenced
this issue
Mar 27, 2020
wajda
added a commit
that referenced
this issue
Mar 27, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Hi team, thanks a lot for this project! We are trying this out in a production setting :)
Not really a bug but I thought this was the best place anyway. Your compose uses variables like
spline.database.connectionUrl
, directly mapping to the webenv variables. Not really convention-friendly i.e.VARIABLE
; Among other things, this is also an issue on some provisioners, such as Azure Container Instances - deploying is not possible because the naming convention - enforced by ACI - prevents it. So something like a wrapper varSPLINE_DATABASE_CONNECTION_URL
could help.Thanks,
cc @patrickdehoon
The text was updated successfully, but these errors were encountered: