Merge pull request #295362 from craigshoemaker/aca/tag-guidance

[Container Apps] Add note to avoid using static tags

Author: prmerger-automator[bot]

articles/container-apps/containers.md

@@ -130,7 +130,7 @@ Most container apps have a single container. In advanced scenarios, an app may a
 
 | Setting | Description | Remarks |
 |---|---|---|
-| `image` | The container image name for your container app. | This value takes the form of `repository/<IMAGE_NAME>:<TAG>`. |
+| `image` | The container image name for your container app. | This value takes the form of `repository/<IMAGE_NAME>:<TAG>`. <br><br>Avoid using using static tags like `latest` for container images. Using static tags can lead to caching problems and can make your app difficult to troubleshoot. Instead, use unique tags for each deployment, such as a Git hash or date and time to ensure that updates are properly tracked and deployed. |
 | `name` | Friendly name of the container. | Used for reporting and identification. |
 | `command` | The container's startup command. | Equivalent to Docker's [entrypoint](https://docs.docker.com/engine/reference/builder/) field.  |
 | `args` | Start up command arguments. | Entries in the array are joined together to create a parameter list to pass to the startup command. |

articles/container-apps/faq.yml

@@ -162,4 +162,9 @@ sections:
           How do I ensure the build and image of my Docker-less build are available in the same region as my app?
         answer: |
           When using `containerapp up` in combination with a Docker-less code base, use the `--location` parameter so that application runs in a location other than US East.
-
+  - name: Tagging
+    questions:
+      - question: |
+          How do I use `latest` or a static tag for my container image?
+        answer: |
+          Avoid using using static tags like `latest` for container images. Using static tags can lead to caching problems and can make your app difficult to troubleshoot. Instead, use unique tags for each deployment, such as a Git hash or date and time to ensure that updates are properly tracked and deployed.