Skip to content
This repository has been archived by the owner on Sep 4, 2019. It is now read-only.

Issue 1852 eval env variables in config values #431

Merged
merged 1 commit into from Feb 5, 2016
Merged

Issue 1852 eval env variables in config values #431

merged 1 commit into from Feb 5, 2016

Conversation

TravisTheTechie
Copy link
Contributor

Adding documentation for NuGet/NuGet.Client#171; the implementation of NuGet/Home#1852


### Environment variables in configuration

Starting with NuGet 3.4, NuGet evaluates environment variables in NuGet.config values.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm just guessing with 3.4 -- will that be right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Thank you for your contribution!

We will merge this documentation when the source is merged.

On Sat, Jan 9, 2016 at 4:24 PM, Travis Smith notifications@github.com
wrote:

In NuGet.Docs/Consume/NuGet-Config-File.md
#431 (comment):

@@ -288,3 +288,24 @@ This results in something more readable (or even manually configurable):

API Key to access package source

Allows you to set the API Key corresponding to a specific package source. This key has to be set via NuGet -SetApiKey + +### Environment variables in configuration + +Starting with NuGet 3.4, NuGet evaluates environment variables in NuGet.config values.

I'm just guessing with 3.4 -- will that be right?


Reply to this email directly or view it on GitHub
https://github.com/NuGet/NuGetDocs/pull/431/files#r49268359.

@csharpfritz
Copy link
Contributor

Publishing now that the PR for the feature has been accepted

csharpfritz added a commit that referenced this pull request Feb 5, 2016
…ables-in-config-values

Issue 1852 eval env variables in config values
@csharpfritz csharpfritz merged commit 3f39a2c into NuGet:master Feb 5, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants