Перейти к файлу
abandyop d3c5d04b5f
Add files via upload
2021-09-16 14:06:55 +05:30
CODE_OF_CONDUCT.md CODE_OF_CONDUCT.md committed 2021-08-28 20:36:46 -07:00
LICENSE LICENSE updated to template 2021-08-28 20:36:47 -07:00
Purview_API_Reference.csv Add files via upload 2021-09-16 14:06:55 +05:30
Purview_API_Reference_Parameters.csv Add files via upload 2021-09-16 14:06:55 +05:30
README.md Update README.md 2021-09-08 13:56:34 +05:30
SECURITY.md SECURITY.md committed 2021-08-28 20:36:48 -07:00
SUPPORT.md SUPPORT.md committed 2021-08-28 20:36:49 -07:00
azure-purview-rest-api-specs.zip Add files via upload 2021-09-08 13:55:16 +05:30

README.md

Azure-Purview-API-via-PowerShell


Execute Azure Purview RESTful APIs via PowerShell


  • Azure Purview REST APIs via Powershell. Based on Purview API Complete Reference and Purview API Docs
  • Note: You need Powershell v7.x.x to use this tool. Please Download and upgrade your Powershell to v7.
  • Extract Purview-API-Powershell.zip to a folder of your choice.
  • Right-Click on the folder and select "PowerShell > Open Here As Administrator" image
  • Run "Purview-API-PowerShell.exe"
  • Note: The file "purview-api-body-payload.json" extracted in the same directory contains the API Body to be sent in case of PUT or POST APIs. Make sure to blank the file first, update your JSON into it and save the file before executing any "PUT" or "POST" APIs. If you need to back up your previous JSONs, you may do so in a different file name, since this file name "purview-api-body-payload.json" is reserved for the next upcoming API call.

Benefits


  • While you can very well use cURL or Postman to Invoke Azure Purview APIs as well, it is generally cumbersome to extract the Azure OAuth2 access_token and use it appropriately in scripts or even during one-time API execution.
  • Powershell has very strong and user friendly integration interfaces with Azure Cloud and hence it makes it really useful to have a way to execute Azure Purview service via its APIs on Windows PowerShell.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.