Skip to content

argocd-pr-env-deploy: revision-only links for mindshub_services - #67

Merged
hamishfagg merged 1 commit into
mainfrom
feat/pr-env-chart-only-links
Sep 25, 2026
Merged

hamishfagg merged 1 commit into
mainfrom
feat/pr-env-chart-only-links

Conversation

@hamishfagg

@hamishfagg hamishfagg commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

What

Deploys: mindshub_services#N on an anchor PR resolves to --helm-set revisions.mindshub_services=<head sha> only, and a mindshub_services PR as the anchor itself gets the same: no ECR lookup, no tags.<repo>. One is_revision_only_repo helper covers both.

Why

mindshub_services ships a SAM stack, deployed per PR env by its pr-env-stacks workflow from the revision on the parent Application. It publishes no image, so the existing path hit RepositoryNotFoundException and failed the deploy.

Part of

  • mindsdb/mindshub_services#227
  • mindsdb/argocd-envs#20
  • mindsdb/Kubernetes-Foundational-Services#156 (mindshub_services as an anchor)

Checks

bash -n on the step script. Deploys: mindshub_services#staging keeps going through the generic staging branch, which also sets an unused tags.mindshub_services; harmless.

🤖 Generated with Claude Code

mindshub_services deploys a SAM stack per PR env from a git revision and
publishes no image, so `Deploys: mindshub_services#N` failed the ECR
existence check. Such links now set revisions.<repo> to the PR head SHA
and nothing else.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@hamishfagg
hamishfagg requested a review from a team as a code owner September 24, 2026 03:55
@hamishfagg
hamishfagg merged commit 7f4d408 into main Sep 25, 2026
6 checks passed
@hamishfagg
hamishfagg deleted the feat/pr-env-chart-only-links branch September 25, 2026 02:27
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