add custom manifests and CRDs via .deployah/#5
Merged
Conversation
Ship raw Kubernetes YAML next to the generated chart: manifests join the Helm release, CRDs apply first with create/create-replace. Fixes #4
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
- refresh deployahVendorHash after go.mod change - add unit tests for extras/deploy/plan/init paths - drop per-flag codecov patch gates (render-only integration)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.deployah/manifests/and.deployah/crds/so users can ship raw Kubernetes YAML next to the generated Helm chart (Bitnami-style escape hatch).--crds create|create-replace, including when the Helm plan is idle.Related
Fixes #4
Test plan
scenarios/(if behavior changes)nix run .#lint/ pre-commit cleanChecklist
README.md,docs/cli/)