Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

offen / docker-volume-backup Public

Notifications You must be signed in to change notification settings
Fork 86
Star 2.1k

Code
Issues 19
Pull requests 2
Discussions
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Security
Insights

Env vars should propagate when using `conf.d`#358

Merged

m90 merged 3 commits intomainoffen/docker-volume-backup:mainfrom env-propagateoffen/docker-volume-backup:env-propagateCopy head branch name to clipboard

Feb 13, 2024

+67-41

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 13, 2024

Extend confd test case to test for env var propagation
m90
committed
Env vars set in conf.d files are expected to propagate
m90
committed
Lock needs to be acquired when instantiating script
m90
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.