Skip to content

Commit 3d054c0

Browse files
authored
Merge pull request #49 from dotnet/sharedenvvars
Sharedenvvars
2 parents 408470a + 7ad76dd commit 3d054c0

File tree

1 file changed

+25
-1
lines changed

1 file changed

+25
-1
lines changed

aspnetcore/test/http-files.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This article contains documentation for:
2121
* [The `.http` file syntax](#http-file-syntax).
2222
* [How to create an `.http` file](#create-an-http-file).
2323
* [How to send a request from an `.http` file](#send-an-http-request).
24-
* [Where to find `.http` file options that can be configured.](#http-file-options).
24+
* [Where to find `.http` file options that can be configured](#http-file-options).
2525
* [How to create requests in `.http` files by using the Visual Studio 2022 **Endpoints Explorer**](#use-endpoints-explorer).
2626

2727
The `.http` file format and editor was inspired by the Visual Studio Code [REST Client extension](https://marketplace.visualstudio.com/items?itemName=humao.rest-client). The Visual Studio 2022 `.http` editor recognizes `.rest` as an alternative file extension for the same file format.
@@ -166,6 +166,30 @@ Visual Studio displays warnings in the following situations:
166166

167167
A variable defined in an environment file can be the same as one defined in the `.http` file, or it can be different. If a variable is defined in both the `.http` file and the environment file, the value in the `.http` file overrides the value in the environment file.
168168

169+
## Shared variables
170+
171+
`$shared` is a special environment name for values that are the same for multiple environments. For example, consider the following environment file (`http-client.env.json`):
172+
173+
```json
174+
{
175+
"$shared": {
176+
"HostAddress": "https://localhost:7293"
177+
},
178+
"dev1": {
179+
"username": "dev1user"
180+
},
181+
"dev2": {
182+
"username": "dev2user"
183+
},
184+
"staging": {
185+
"username": "staginguser",
186+
"HostAddress": "https://staging.contoso.com"
187+
}
188+
}
189+
```
190+
191+
In the preceding example, the `$shared` environment defines the `HostAddress` variable with the value `localhost:7293`. This variable with this value functions as a default for any environment that doesn't define a `HostAddress` variable. When you use the `dev1` or `dev2` environment, the value for `HostAddress` comes from the `$shared` environment because `dev1` and `dev2` don't define a `HostAddress` variable. When you use the `staging` environment, the value for `HostAddress` is set to `https://staging.contoso.com`, overriding the `$shared` default.
192+
169193
## User-specific environment files
170194

171195
A user-specific value is any value that an individual developer wants to test with but doesn’t want to share with the team. Since the `http-client.env.json` file is checked in to source control by default, it wouldn’t be appropriate to add user-specific values to this file. Instead, put them in a file named `http-client.env.json.user` located in the same folder as the `http-client.env.json` file. Files that end with `.user` should be excluded from source control by default when using Visual Studio source control features.

0 commit comments

Comments
 (0)