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

Remove jq in FHIR access token lookup #59412

Merged
merged 1 commit into from Jul 21, 2020
Merged

Remove jq in FHIR access token lookup #59412

merged 1 commit into from Jul 21, 2020

Conversation

c-w
Copy link
Contributor

@c-w c-w commented Jul 21, 2020

Currently the FHIR documentation on how to look up an access token for the FHIR Server using the Azure CLI depends on the external tool jq to extract specific items from JSON payloads returned by the CLI.

However, the Azure CLI supports querying the JSON responses natively via --query. As such, this change updates the documentation to use --query instead of jq which removes an external tool dependency and also makes the Azure CLI snippets work on Windows.

Currently the FHIR documentation on how to look up an access token for the FHIR Server using the Azure CLI depends on the external tool `jq` to extract specific items from JSON payloads returned by the CLI.

However, the Azure CLI supports querying the JSON responses natively via [--query](https://docs.microsoft.com/en-us/cli/azure/query-azure-cli). As such, this change updates the documentation to use `--query` instead of `jq` which removes an external tool dependency and also makes the Azure CLI snippets work on Windows.
@PRMerger19
Copy link
Collaborator

PRMerger19 commented Jul 21, 2020

@c-w : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver ktoliver merged commit d1c00f4 into MicrosoftDocs:master Jul 21, 2020
1 check passed
@c-w c-w deleted the patch-1 branch Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants