Configurations: 'specification/orbitalplanetarycomputer/Orbital.Management/tspconfig.yaml', API Version: 2026-04-15, SDK Release Type: stable, and CommitSHA: '5e21babae10dd7056c3005bb51da815f0495f1aa' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6062570 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release. **Release plan link:** [https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=0ae5a917-5001-f111-8406-000d3a376cbb](https://web.powerapps.com/apps/821ab569-ae60-420d-8264-d7b5d5ef734c?release-plan-id=0ae5a917-5001-f111-8406-000d3a376cbb) **Submitted by**: [email protected] ## Release Plan Details - Release Plan: https://aka.ms/sdk-release-planner?release-plan-id=0ae5a917-5001-f111-8406-000d3a376cbb Spec pull request: https://github.com/Azure/azure-rest-api-specs/pull/41263 Spec API version: 04-15-2026 --------- Co-authored-by: Devanshu Singh <[email protected]>
4.5 KiB
@azure/arm-planetarycomputer client library samples for JavaScript
These sample programs show how to use the JavaScript client libraries for @azure/arm-planetarycomputer in some common scenarios.
| File Name | Description |
|---|---|
| geoCatalogsCreateSample.js | create a GeoCatalog x-ms-original-file: 2026-04-15/GeoCatalogs_Create.json |
| geoCatalogsDeleteSample.js | delete a GeoCatalog x-ms-original-file: 2026-04-15/GeoCatalogs_Delete.json |
| geoCatalogsGetSample.js | get a GeoCatalog x-ms-original-file: 2026-04-15/GeoCatalogs_Get.json |
| geoCatalogsListByResourceGroupSample.js | list GeoCatalog resources by resource group x-ms-original-file: 2026-04-15/GeoCatalogs_ListByResourceGroup.json |
| geoCatalogsListBySubscriptionSample.js | list GeoCatalog resources by subscription ID x-ms-original-file: 2026-04-15/GeoCatalogs_ListBySubscription.json |
| geoCatalogsUpdateSample.js | update a GeoCatalog x-ms-original-file: 2026-04-15/GeoCatalogs_Update.json |
Prerequisites
The sample programs are compatible with LTS versions of Node.js.
You need an Azure subscription to run these sample programs.
Samples retrieve credentials to access the service endpoint from environment variables. Alternatively, edit the source code to include the appropriate credentials. See each individual sample for details on which environment variables/credentials it requires to function.
Adapting the samples to run in the browser may require some additional consideration. For details, please see the package README.
Setup
To run the samples using the published version of the package:
- Install the dependencies using
npm:
npm install
-
Edit the file
sample.env, adding the correct credentials to access the Azure service and run the samples. Then rename the file fromsample.envto just.env. The sample programs will read this file automatically. -
Run whichever samples you like (note that some samples may require additional setup, see the table above):
node geoCatalogsCreateSample.js
Alternatively, run a single sample with the required environment variables set (setting up the .env file is not required if you do this), for example (cross-platform):
node geoCatalogsCreateSample.js
Next Steps
Take a look at our API Documentation for more information about the APIs that are available in the clients.