Skip to content
This repository was archived by the owner on Sep 21, 2026. It is now read-only.

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

Merged
levivannoort merged 1 commit into
mainfrom
chore/deploy-to-application-configuration
Aug 16, 2026
Merged

levivannoort merged 1 commit into
mainfrom
chore/deploy-to-application-configuration

Conversation

@levivannoort

Copy link
Copy Markdown
Member

What

website moved out of assets-applications into application-configuration (appwrite-labs/application-configuration#12), which is laid out as <project>/<env>/<app> instead of <env>/<app>.

Affected workflows: production,staging.

-  PROJECT: website
+  PROJECT: assets
+  APPLICATION: website
-  DECLARATIVE_REPOSITORY: assets-applications
+  DECLARATIVE_REPOSITORY: application-configuration

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

PROJECT now names the project and APPLICATION the app, matching the dns workflows already deploying to that repo. The commit subject still names the app, so the bump commits read the same as before.

The declarative-deployment GitHub App is already installed on application-configuration — it is what the dns pipeline authenticates with.

Merge order

Last. ArgoCD has to be reading the new repo first, otherwise a bump lands where nothing syncs from. Order: appwrite-labs/reusable-workflows#10 → appwrite-labs/application-configuration#12 → appwrite-labs/cluster-configuration-generator#158 (plus its generated PR into cluster-configuration) → this.

website moved out of appwrite-labs/assets-applications into the consolidated
appwrite-labs/application-configuration repository, which is laid out as
<project>/<env>/<app> instead of <env>/<app>. PROJECT now names the
project and APPLICATION the app, matching the dns workflows already
deploying there; the commit subject keeps naming the app.

The values were moved byte-identical and ArgoCD is repointed in
cluster-configuration-generator, so this only changes where the bump is
written.
@appwrite

appwrite Bot commented Aug 16, 2026 •

Copy link
Copy Markdown

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Ready Ready View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Building Building View Logs Preview URL QR Code


Tip

Roll back Sites deployments instantly by switching between versions

@greptile-apps

greptile-apps Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR redirects production and staging image-tag bumps from assets-applications to the consolidated application-configuration repository.

  • Introduces separate PROJECT (assets) and APPLICATION (website) variables.
  • Updates manifest paths to assets/<environment>/website/default.yaml.
  • Preserves application-oriented bump commit messages.

Confidence Score: 5/5

The PR appears safe to merge after the coordinated external repository and ArgoCD changes described in the required merge order.

Both workflows consistently use the new repository, static project/application path segments, and application name, with no internally inconsistent or concretely broken changed path identified.

Important Files Changed

Filename Overview
.github/workflows/production.yml Consistently updates repository authentication, checkout, manifest path, staging path, and commit subject for the production deployment bump.
.github/workflows/staging.yml Mirrors the production migration consistently for the staging deployment bump.

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

@levivannoort
levivannoort merged commit d8403ad into main Aug 16, 2026
6 of 7 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants