Comments (5)
Would the result of summon printenv | egrep 'FOO|BAR' be FOO=foo-base or FOO=foo-common?
Based on some other observations, what I've seen is that "last thing defined, wins". So in your example, I would expect to see FOO=foo-common
. But that is just my intuition, and I do not feel strongly about that opinion at all.
To be honest though, I hadn't thought to combine an implicit base section along with an explicit common
section. The docs kinda sorta made me think that you could either define sections xor everything was required to live in the base section.
Perhaps this issue can simply be converted into a request for more explicit examples in the docs?
from summon.
This one is a bit tricky since we would need to figure out if the user really want to use the common
section.
This example kind of illustrates it:
FOO: foo-base
common:
FOO: foo-common
production:
BAR: bar
Would the result of summon printenv | egrep 'FOO|BAR'
be FOO=foo-base
or FOO=foo-common
?
I think if you use -e
, we assume that you have split out things into sections but if you don't specify it, it gets ambiguous as to what you intended. I think a solution could be implemented easy but we would need to know what precedence to apply to the common
section if you have a variable in both toplevel and common
grouping.
Let me chew on this a bit this week.
from summon.
Yeah I think that putting this in the docs would be the best place since current behavior iirc from playing around with this yesterday is that it's doing an xor
on evaluation already which matches the docs but maybe that's not clear enough? I'll reword the issue/title a bit to match.
from summon.
Works for me, thanks!
from summon.
I'd like to give this a little push... I do have quite some secrets to inject an only for special purposes I need to overwrite some of them. So the combination of section-less common part with a section for specific secrets would help me a lot. with the current implementation I'd always need to provide an explicit -e common
parameter to actually read te default values. that's not very intuitive.
For me It would already be sufficient to support one of the following solutions: either allow section-less common part (and always load it) OR have a common
section, but load it also in case NO environment has been given.
P.S.: another problem currently is that if you have a section-less part and a section summon
throws lots of errors in case you actually provide the -e section
parameter. So a section-less common part with some additional section secrets does not work right now
from summon.
Related Issues (20)
- Go version is updated to 1.15
- Specify (non-variable) tempfile name HOT 7
- Summon pipeline runs using GitHub actions instead of a private Jenkins server
- Summon builds are unstable HOT 2
- Inject summon secrets into docker containers using --env HOT 2
- Summon README is missing a couple flags
- Make list of environment variable names available in child process HOT 1
- Spike: Zero-change Summon deployment HOT 3
- Spike: scaling Summon installs into Kubernetes volume mounts HOT 2
- Spike: ensuring trust of the Summon executable HOT 1
- There are diagrams and flow charts that show how Summon is used in Kubernetes HOT 6
- Review the proposals for zero-change Summon deployment in Kubernetes with the security architect HOT 2
- Summon as an Alpine package HOT 1
- There is a v0.8.4 release of Summon HOT 1
- Default provider path is hard-coded rather than using homebrew directory on OS X
- There is support for the new Apple silicon
- Add templating support for ephemeral cred/config files
- Docker Secrets documentation has broken links
- Default not supported for `gopass`
- Support for ARM64
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from summon.