You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. shell-script), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-bash
FOO=BARto make it available as a shell variable in the "main" shell instance, orexport FOO=BARto make it available in that shell and in the environment of processes started from it. I'm not exactly at all sure why you'd run another shell here?export SECRET_NAME=SECRET_VALUEso that the container can rus the commandbash -c 'source /path/to/file' && npm startand. Yet none of the secrets I set in this script are available in any shell I start on the container later on.bash -c 'source /path/to/file' && npm start'the env vars set by the sourced script should be available tonpmthere. But there's no "global" environment where env vars would be set: they're only inherited to child processes, not to the parent, to to siblings.npm startusingprocess.env.VAR_NAME, the variable isundefined. I am very confused that this does not work given that I am doing the very same thing described in this example: vaultproject.io/docs/platform/k8s/injector/…