Skip to content

fix(deploy): validate the project file with its env files when publishing - #121

Merged
ExtraToast merged 1 commit into
mainfrom
fix/validate-with-env
Oct 27, 2026
Merged

ExtraToast merged 1 commit into
mainfrom
fix/validate-with-env

Conversation

@ExtraToast

Copy link
Copy Markdown
Contributor

Summary

v0.21.0's fragment never published. Publish Fragment validated deploy/auth.project.yml on its own, and on deploy-kit 1.0 that file alone is refused: the auth-api Process's transit grant needs the Vault client that deploy/env/auth-api/base.env wires with ${identity:vaultRole}.

  • validate-with: deploy/env makes the workflow read the env files together with the project file, as the pack step already does.

Test plan

  • deploy-kit validate deploy/auth.project.yml on 1.0.0: E_SELF_WITHOUT_VAULT_CLIENT, which is the failure from run 40527227240
  • deploy-kit validate deploy/auth.project.yml deploy/env on 1.0.0: accepted (3 read)
  • The next release's Publish run publishes the fragment, and pulling it by digest reads schemaVersion 1.0.0

Part of JorisJonkers-dev/deploy-kit#195. Part of #119.

…hing

On deploy-kit 1.0 the auth-api Process's transit grant needs the Vault client its env file wires (${identity:vaultRole}). Publish Fragment validated the project file alone, so the v0.21.0 fragment was refused with E_SELF_WITHOUT_VAULT_CLIENT and never published.

Part of #119
@ExtraToast ExtraToast added type: bug Something is broken or behaving incorrectly. area: deploy homelab-deploy, deploy-v2, manifests, and rollout flow. priority: P1 High; important and should be handled in the current iteration. labels Oct 27, 2026
@ExtraToast ExtraToast self-assigned this Oct 27, 2026
@ExtraToast
ExtraToast enabled auto-merge (squash) October 27, 2026 15:13
@ExtraToast
ExtraToast merged commit 3680745 into main Oct 27, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: deploy homelab-deploy, deploy-v2, manifests, and rollout flow. priority: P1 High; important and should be handled in the current iteration. type: bug Something is broken or behaving incorrectly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant