Blueprint Config option to make Environment Groups non-additive per service
M
Marlowe Lankford
At the moment, when you change any service's environment fromGroup field to another env group (on same line), it links that group to the service but the env group that was replaced on the fromGroup line remains as a linked env group.
It would be nice to configure a blueprint to replace an environment group when you edit fromGroup inline.
ex.:
services:
- type: web
- name: test-service
...
envVars:
- fromGroup: test-env-1
^ If we changed 'test-env-1' to 'test-env-2' on the same line, 'test-service' would have BOTH test-env-1 and test-env-2 linked. My request is that it just replaced the linked group.
Log In