Skip to content

Commit 4999778

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into vnet-flow-logs-overview
2 parents 5f7afd6 + 0b05d1b commit 4999778

File tree

7 files changed

+10
-36
lines changed

7 files changed

+10
-36
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22531,6 +22531,11 @@
2253122531
"source_path_from_root": "/articles/virtual-network/ip-services/virtual-networks-static-private-ip-classic-ps.md",
2253222532
"redirect_url": "/updates/azure-classic-resource-providers-will-be-retired-on-31-august-2024/",
2253322533
"redirect_document_id": false
22534+
},
22535+
{
22536+
"source_path_from_root": "/articles/orbital/overview-analytics.md",
22537+
"redirect_url": "/azure/orbital/overview",
22538+
"redirect_document_id": false
2253422539
}
2253522540
]
2253622541
}

articles/operator-nexus/howto-cluster-runtime-upgrade.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,7 @@ az networkcloud cluster show --cluster-name "clusterName" --resource-group "reso
8787
```
8888

8989
The output should be the target cluster's information and the cluster's detailed status and detail status message should be present.
90+
For more detailed insights on the upgrade progress, the individual BMM in each Rack can be checked for status. Example of this is provided in the reference section under [BareMetal Machine roles](./reference-near-edge-baremetal-machine-roles.md).
9091

9192
## Configure compute threshold parameters for runtime upgrade using cluster updateStrategy
9293
The following Azure CLI command is used to configure the compute threshold parameters for a runtime upgrade:

articles/orbital/TOC.yml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ items:
77
href: overview.md
88
- name: About Microsoft and partner ground stations
99
href: about-ground-stations.md
10-
1110
- name: Quickstart
1211
items:
1312
- name: Get started with Azure Orbital Ground Station
@@ -59,3 +58,5 @@ items:
5958
href: organize-stac-data.md
6059
- name: Process Synthetic Aperture Radar (SAR) data
6160
href: sar-reference-architecture.md
61+
- name: Process Aqua satellite data using NASA-provided tools
62+
href: satellite-imagery-with-orbital-ground-station.md

articles/orbital/overview-analytics.md

Lines changed: 0 additions & 33 deletions
This file was deleted.
78.5 KB
Loading
100 KB
Loading

articles/spring-apps/quickstart-deploy-apps.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -424,10 +424,10 @@ To deploy to Azure, you must sign in with your Azure account with Azure Toolkit
424424
1. In the **Name** field, append *:api-gateway* to the existing **Name**.
425425
1. In the **Artifact** textbox, select *spring-petclinic-api-gateway-3.0.1*.
426426
1. In the **Subscription** textbox, verify your subscription.
427-
1. In the **Spring Cloud** textbox, select the instance of Azure Spring Apps that you created in [Provision Azure Spring Apps instance](./quickstart-provision-service-instance.md).
428-
1. Set **Public Endpoint** to *Enable*.
427+
1. In the **Spring Apps** textbox, select the instance of Azure Spring Apps that you created in [Provision Azure Spring Apps instance](./quickstart-provision-service-instance.md).
429428
1. In the **App:** textbox, select **Create app...**.
430429
1. Enter *api-gateway*, then select **OK**.
430+
1. Set **Public Endpoint** to *Enable*.
431431
1. Specify the memory to 2 GB and JVM options: `-Xms2048m -Xmx2048m`.
432432

433433
:::image type="content" source="media/quickstart-deploy-apps/memory-jvm-options.png" alt-text="Screenshot of memory and JVM options." lightbox="media/quickstart-deploy-apps/memory-jvm-options.png":::

0 commit comments

Comments
 (0)