Basic Argo Manifest Template Examples added

src/pages/docs/argo-cd/steps/update-application-manifests.md

@@ -81,3 +81,26 @@ When deploying a release containing an Update Argo CD Applications Manifest step
 If an input template references a [Sensitive Variable](/docs/projects/variables/sensitive-variables), the deployment will fail.
 This ensures sensitive data is not persisted in the target Git repository in plain text.
 :::
+
+## Example Manifests
+
+### Config Map
+
+The following represents a template of a configmap.
+The database_url is set via the user-specified project variable `DB_NAME`, whose value can change based on Octopus variable scoping mechanisms (e.g. via environment or tenant).
+
+The time of the deployment, defined in the inbuilt `Octopus.Deployment.Created`, is written to the `deployment_created_at` field.
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: my-app-config
+data:
+  # Key-value pairs for configuration data
+  log_level: INFO
+  directory: "#{Octopus.Environment.Name}"
+  feature_flag_enabled: "true"
+  database_url: "jdbc:postgresql://mydb.example.com:5432/#{DB_NAME}"
+  deployment_created_at: "#{Octopus.Deployment.Created}"
+```