Merge pull request #209288 from leonard520/config-limit

Add notice about config server/ACS limitation

Author: prmerger-automator[bot]

articles/spring-apps/how-to-config-server.md

@@ -51,6 +51,9 @@ Azure Spring Apps supports Azure DevOps, GitHub, GitLab, and Bitbucket for stori
 
 Additionally, some configurable properties are available only for certain types. The following subsections list the properties for each repository type.
 
+> [!NOTE]
+> Config Server takes `master` (on Git) as the default label if you don't specify one. However, GitHub has recently changed the default branch from `master` to `main`. To avoid Azure Spring Apps Config Server failure, be sure to pay attention to the default label when setting up Config Server with GitHub, especially for newly-created repositories.
+
 ### Public repository
 
 When you use a public repository, your configurable properties are more limited.
@@ -84,7 +87,7 @@ All configurable properties used to set up private Git repository with SSH are l
 | `strict-host-key-checking` | No     | Indicates whether the Config Server instance will fail to start when using the private `host-key`. Should be *true* (default value) or *false*. |
 
 > [!NOTE]
-> Config Server takes `master` (om Git itself) as the default label if you don't specify one. But GitHub has changed the default branch from `master` to `main` recently. To avoid Azure Spring Apps Config Server failure, be sure to pay attention to the default label when setting up Config Server with GitHub, especially for newly-created repositories.
+> Config Server doesn't support SHA-2 signatures yet and we are actively working on to support it in future release. Before that, please use SHA-1 signatures or basic auth instead.
 
 ### Private repository with basic authentication
 

articles/spring-apps/how-to-enterprise-application-configuration-service.md

@@ -85,6 +85,9 @@ The following image shows the three types of repository authentication supported
    | Host key algorithm       | No        | The algorithm for `hostKey`: one of `ssh-dss`, `ssh-rsa`, `ecdsa-sha2-nistp256`, `ecdsa-sha2-nistp384`, and `ecdsa-sha2-nistp521`. (Required if supplying `Host key`).                                                              |
    | Strict host key checking | No        | Optional value that indicates whether the backend should be ignored if it encounters an error when using the provided `Host key`. Valid values are `true` and `false`. The default value is `true`.                                 |
 
+> [!NOTE]
+> Application Configuration Service for Tanzu doesn't support SHA-2 signatures yet and we are actively working on to support it in future release. Before that, please use SHA-1 signatures or basic auth instead.
+
 To validate access to the target URI, select **Validate**. After validation completes successfully, select **Apply** to update the configuration settings.
 
 ## Refresh strategies