chore(deploy): push image bumps to application-configuration

[levivannoort]

What

The cloud values moved out of cloud-applications into application-configuration (appwrite-labs/application-configuration#15), laid out as <project>/<env>/<app> instead of <env>/<app>.

+    PROJECT: cloud
+    APPLICATION: cloud
-    DECLARATIVE_REPOSITORY: cloud-applications
+    DECLARATIVE_REPOSITORY: application-configuration

-  ${{ env.ENVIRONMENT }}/cloud/default.yaml
+  ${{ env.PROJECT }}/${{ env.ENVIRONMENT }}/${{ env.APPLICATION }}/default.yaml

The path was hardcoded; it now builds from the env vars like every other deploy workflow. The tag still lands on the cloud-console alias inside the cloud release, and production still opens a reviewed PR against the declarative repo rather than pushing to main.

Verified: both write targets resolve to real files in the new repo and carry a cloud-console.image.tag key.

Merge order

Last. ArgoCD has to be reading the new repo first: appwrite-labs/application-configuration#15 → appwrite-labs/cluster-configuration-generator#163 (plus its generated PR into cluster-configuration) → this.

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Building	View Logs	Preview URL

Tip

Sites support three domain rule types: Active deployment, Git branch, and Redirect

[greptile-apps]

Greptile Summary

This PR redirects staging and production image-tag updates from cloud-applications to the newly structured application-configuration repository.

• Adds project and application workflow variables and uses them to construct the new values-file paths.
• Preserves direct staging promotion and the reviewed production pull-request flow.
• Updates deployment concurrency comments to reflect the new repository.

Confidence Score: 5/5

The PR appears safe to merge after the documented declarative-repository migration prerequisites are complete.

The new repository, path construction, alias, and environment-specific promotion behavior are internally consistent, and no concrete changed-code failure remains.

Important Files Changed

Filename	Overview
.github/workflows/production.yml	Moves production tag promotion to application-configuration at cloud/production/cloud/default.yaml while retaining the reviewed pull-request workflow.
.github/workflows/staging.yml	Moves staging tag promotion to application-configuration at cloud/staging/cloud/default.yaml while retaining direct pushes to main.

_{Reviews (1): Last reviewed commit: "chore(deploy): push image bumps to appli..." | Re-trigger Greptile}