Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[KeyVault] dotenv fix #4533

Merged
merged 1 commit into from
Jul 30, 2019
Merged

[KeyVault] dotenv fix #4533

merged 1 commit into from
Jul 30, 2019

Conversation

sadasant
Copy link
Contributor

With this change, we can have a .env file in sdk/keyvault (the parent
folder, as well as with other of our projects using dotenv) with the
following properties:

AZURE_CLIENT_ID=XXXXXXXX
AZURE_CLIENT_SECRET=XXXXXXXX
AZURE_TENANT_ID=XXXXXXXX
KEYVAULT_NAME=XXXXXXXX
TEST_MODE=["record" or "playback", without quotes]

And then run rushx integration-test:node to record (or playback) all
the tests with the Node environment, and also rushx integration-test:browser
to run the tests with the browser environment.

Would this help with #4389 ?

Note: The recorder already replaces all the environment variables with stub values! Only TEST_MODE=playback is needed to run the playback tests.

Please review 💙

With this change, we can have a `.env` file in `sdk/keyvault` (the parent
folder, as well as with other of our projects using dotenv) with the
following properties:

```
AZURE_CLIENT_ID=XXXXXXXX
AZURE_CLIENT_SECRET=XXXXXXXX
AZURE_TENANT_ID=XXXXXXXX
KEYVAULT_NAME=XXXXXXXX
TEST_MODE=["record" or "playback", without quotes]
```

And then run `rushx integration-test:node` to record (or playback) all
the tests with the Node environment, and also `rushx integration-test:browser`
to run the tests with the browser environment.

Would this help with Azure#4389 ?

Please review 💙
@sadasant sadasant added Client This issue points to a problem in the data-plane of the library. KeyVault labels Jul 30, 2019
@sadasant sadasant requested a review from sophiajt July 30, 2019 19:23
@sadasant sadasant self-assigned this Jul 30, 2019
@sadasant
Copy link
Contributor Author

This will work in the root directory of both projects. The main issue that this solves is that, once rollup was added, the path changed since the output file is now located elsewhere. This output file is not expected to change locations anytime soon, so we won't need to change it in the foreseeable future.

@sadasant sadasant merged commit 39a30e8 into Azure:master Jul 30, 2019
@sadasant sadasant deleted the feature/fix4389 branch July 30, 2019 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. KeyVault
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants