Skip to content

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

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

chore(deploy): push image bumps to application-configuration#21
levivannoort merged 1 commit into
mainfrom
chore/deploy-to-application-configuration

Conversation

@levivannoort

Copy link
Copy Markdown
Member

What

mcp-for-docs 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.

-  PROJECT: mcp-for-docs
+  PROJECT: assets
+  APPLICATION: mcp-for-docs
-  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.

mcp-for-docs 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.
@greptile-apps

greptile-apps Bot commented Aug 16, 2026

Copy link
Copy Markdown

Greptile Summary

This PR redirects production image-tag bumps to the new application-configuration repository and its project/environment/application layout.

  • Changes the declarative repository from assets-applications to application-configuration.
  • Separates the assets project from the mcp-for-docs application.
  • Updates the manifest path, staged file, and bump commit subject accordingly.

Confidence Score: 5/5

The PR appears safe to merge, provided the documented deployment migration order has been completed.

The checkout remains rooted at the selected declarative repository, and the edit and staging commands consistently target the newly documented project/environment/application path.

Important Files Changed

Filename Overview
.github/workflows/production.yml Updates the production deployment workflow’s repository, manifest path, and commit metadata consistently; no actionable defect was established.

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

@levivannoort
levivannoort merged commit 9790908 into main Aug 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants