Add .fips-template.yaml to opt into fips-agents patch flow#39
Merged
Conversation
Without this manifest, the fips-agents-cli refuses to run `fips-agents patch` against gateway projects — its `get_categories_for_type` raises for gateway / ui / sandbox project types because no hardcoded category set exists for them. The presence of this file is what makes the patch flow work for projects scaffolded from this template. Schema: schema_version: 1, with three categories (chart, docs, build) and a 13-entry never_patch list separating template-managed scaffolding from the user's Go source, deploy values, and helper scripts. Categories deliberately match the names of CLI subcommands the user already has (`fips-agents patch chart`, `patch docs`, `patch build`) so a future agent / mcp / gateway user has the same muscle memory across project types. Companion to fips-agents/fips-agents-cli#48 (the loader). Older CLI installs that don't know about .fips-template.yaml will simply ignore the file — nothing breaks. Assisted-by: Claude Code (Opus 4.7)
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
1 participant
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.
Companion PR to fips-agents/fips-agents-cli#48 (the manifest loader). After both merge, `fips-agents patch` will work for projects scaffolded from this template — it doesn't today, because the CLI's hardcoded fallback raises `ValueError` for the `gateway` project type.
What
Adds `.fips-template.yaml` at the repo root with `schema_version: 1`. Three categories declared:
Plus a 13-entry `never_patch` list:
What this enables
After the CLI loader (fips-agents/fips-agents-cli#48) ships:
```bash
$ fips-agents patch check
Available Updates
┏━━━━━━━━━━┳━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Category ┃ Files Changed ┃ Description ┃
┡━━━━━━━━━━╇━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ build │ 1 │ Build and deployment files │
└──────────┴───────────────┴────────────────────────────┘
```
Today this same command crashes with `ValueError: Patching is not supported for project type 'gateway'`.
Compatibility
Older CLI installs that don't know about `.fips-template.yaml` continue to refuse `patch` for gateway projects exactly as before. The file is invisible to them, so this PR is non-breaking.
Test plan