Skip to content

Commit b45e673

Browse files
TimShererWithAquentTimShererWithAquent
committed
Address warnings.
1 parent d2b4cfc commit b45e673

9 files changed

+19
-19
lines changed

‎articles/app-service/includes/quickstart-php/quickstart-php-windows-pivot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -127,7 +127,7 @@ To complete this quickstart:
127127
remote: Finished successfully.
128128
remote: Running post deployment command(s)...
129129
remote: Deployment successful.
130-
To \<URL>
130+
To &lt;URL>
131131
cc39b1e..25f1805 main -> main
132132
</pre>
133133

‎articles/app-service/tutorial-dotnetcore-sqldb-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -670,7 +670,7 @@ With the SQL Database protected by the virtual network, the easiest way to run d
670670
1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:
671671
672672
<pre>
673-
Open SSH session to App Service container at: \<URL>
673+
Open SSH session to App Service container at: &lt;URL>
674674
</pre>
675675
676676
1. In the SSH session, run the following commands:
@@ -696,7 +696,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
696696
Deploying services (azd deploy)
697697

698698
(✓) Done: Deploying service web
699-
- Endpoint: \<URL>
699+
- Endpoint: &lt;URL>
700700
</pre>
701701

702702
2. Add a few tasks to the list.
@@ -718,7 +718,7 @@ The sample application includes standard logging statements to demonstrate this
718718
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
719719
720720
<pre>
721-
Stream App Service logs at: \<URL>
721+
Stream App Service logs at: &lt;URL>
722722
</pre>
723723
724724
Learn more about logging in .NET apps in the series on [Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python and Java applications](/azure/azure-monitor/app/opentelemetry-enable?tabs=aspnetcore).

‎articles/app-service/tutorial-java-jboss-mysql-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -538,7 +538,7 @@ In this step, you use the SSH connection to the app container to verify the JNDI
538538
1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:
539539

540540
<pre>
541-
Open SSH session to App Service container at: \<URL>
541+
Open SSH session to App Service container at: &lt;URL>
542542
</pre>
543543

544544
1. In the SSH terminal, run `$JBOSS_HOME/bin/jboss-cli.sh --connect`.
@@ -609,7 +609,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
609609
Deploying services (azd deploy)
610610
611611
(✓) Done: Deploying service web
612-
- Endpoint: \<URL>
612+
- Endpoint: &lt;URL>
613613
</pre>
614614
615615
2. Add a few tasks to the list.
@@ -631,7 +631,7 @@ The sample application includes standard Log4j logging statements to demonstrate
631631
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
632632

633633
<pre>
634-
Stream App Service logs at: \<URL>
634+
Stream App Service logs at: &lt;URL>
635635
</pre>
636636

637637
Learn more about logging in Java apps in the series on [Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python, and Java applications](/azure/azure-monitor/app/opentelemetry-enable?tabs=java).

‎articles/app-service/tutorial-java-spring-cosmosdb.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -556,7 +556,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
556556
Deploying services (azd deploy)
557557
558558
(✓) Done: Deploying service web
559-
- Endpoint: \<URL>
559+
- Endpoint: &lt;URL>
560560
</pre>
561561
562562
2. Add a few tasks to the list.
@@ -578,7 +578,7 @@ The sample application includes standard Log4j logging statements to demonstrate
578578
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
579579

580580
<pre>
581-
Stream App Service logs at: \<URL>
581+
Stream App Service logs at: &lt;URL>
582582
</pre>
583583

584584
Learn more about logging in Java apps in the series on [Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python and Java applications](/azure/azure-monitor/app/opentelemetry-enable?tabs=java).

‎articles/app-service/tutorial-java-tomcat-mysql-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -571,7 +571,7 @@ In this step, you use the SSH connection to the app container to verify the JNDI
571571
1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:
572572

573573
<pre>
574-
Open SSH session to App Service container at: \<URL>
574+
Open SSH session to App Service container at: &lt;URL>
575575
</pre>
576576

577577
1. In the SSH terminal, run `cat /usr/local/tomcat/conf/context.xml`. You should see that a JNDI resource called `jdbc/AZURE_MYSQL_CONNECTIONSTRING_DS` was added. You use this data source later.
@@ -643,7 +643,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
643643
Deploying services (azd deploy)
644644
645645
(✓) Done: Deploying service web
646-
- Endpoint: \<URL>
646+
- Endpoint: &lt;URL>
647647
</pre>
648648
649649
2. Add a few tasks to the list.
@@ -665,7 +665,7 @@ The sample application includes standard Log4j logging statements to demonstrate
665665
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
666666

667667
<pre>
668-
Stream App Service logs at: \<URL>
668+
Stream App Service logs at: &lt;URL>
669669
</pre>
670670

671671
Learn more about logging in Java apps in the series on [Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python, and Java applications](/azure/azure-monitor/app/opentelemetry-enable?tabs=java).

‎articles/app-service/tutorial-nodejs-mongodb-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -616,7 +616,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
616616
Deploying services (azd deploy)
617617
618618
(✓) Done: Deploying service web
619-
- Endpoint: \<URL>
619+
- Endpoint: &lt;URL>
620620
</pre>
621621
622622
2. Add a few tasks to the list.
@@ -636,7 +636,7 @@ Azure App Service captures all messages logged to the console to assist you in d
636636
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
637637

638638
<pre>
639-
Stream App Service logs at: \<URL>
639+
Stream App Service logs at: &lt;URL>
640640
</pre>
641641

642642
Learn more about logging in Java apps in the series on [Enable Azure Monitor OpenTelemetry for .NET, Node.js, Python and Java applications](/azure/azure-monitor/app/opentelemetry-enable?tabs=java).

‎articles/app-service/tutorial-php-mysql-app.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -697,7 +697,7 @@ With the MySQL database protected by the virtual network, the easiest way to run
697697
1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:
698698
699699
<pre>
700-
Open SSH session to App Service container at: \<URL>
700+
Open SSH session to App Service container at: &lt;URL>
701701
</pre>
702702
703703
1. In the SSH session, run database migrations from the */home/site/wwwroot* directory:
@@ -723,7 +723,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
723723
Deploying services (azd deploy)
724724
725725
(✓) Done: Deploying service web
726-
- Endpoint: \<URL>
726+
- Endpoint: &lt;URL>
727727
</pre>
728728
729729
2. Add a few tasks to the list.
@@ -745,7 +745,7 @@ The sample app outputs console log messages in each of its endpoints to demonstr
745745
In the AZD output, find the link to stream App Service logs and navigate to it in the browser. The link looks like this in the AZD output:
746746
747747
<pre>
748-
Stream App Service logs at: \<URL>
748+
Stream App Service logs at: &lt;URL>
749749
</pre>
750750
751751
Having issues? Check the [Troubleshooting section](#troubleshooting).

‎articles/app-service/tutorial-python-postgresql-app-fastapi.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -497,7 +497,7 @@ In this section, you'll run this command manually for demonstration purposes. Wi
497497
Deploying services (azd deploy)
498498
499499
(✓) Done: Deploying service web
500-
- Endpoint: \<URL>
500+
- Endpoint: &lt;URL>
501501
</pre>
502502
503503
2. Add a few restaurants to the list.

‎articles/app-service/tutorial-python-postgresql-app-flask.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -619,7 +619,7 @@ With the PostgreSQL database protected by the virtual network, the easiest way t
619619
1. In the AZD output, find the URL for the SSH session and navigate to it in the browser. It looks like this in the output:
620620

621621
<pre>
622-
Open SSH session to App Service container at: \<URL>
622+
Open SSH session to App Service container at: &lt;URL>
623623
</pre>
624624

625625
1. In the SSH session, run `flask db upgrade`. If it succeeds, App Service is [connecting successfully to the database](#i-get-an-error-when-running-database-migrations).

0 commit comments

Comments
 (0)