Skip to content

chore(manifest): never reap cloud targets - #160

Closed
JeroenSoeters wants to merge 1 commit into
mainfrom
chore/never-reap-manifest
Closed

chore(manifest): never reap cloud targets#160
JeroenSoeters wants to merge 1 commit into
mainfrom
chore/never-reap-manifest

Conversation

@JeroenSoeters

Copy link
Copy Markdown
Contributor

Declares NeverReap as this plugin's manifest default reaping behaviour: a cloud provider region cannot be deleted out of band, so reaping — which exists for targets whose backing infrastructure can go away — must never apply to its targets. An explicit per-target reaping still wins. Takes effect with platform-engineering-labs/formae#756, which wires manifest reaping defaults into target admission.

A cloud provider region cannot be deleted out of band, so reaping,
which exists for targets whose backing infrastructure can go away,
must never apply to this plugin's targets. Declare NeverReap as the
manifest default; an explicit per-target reaping still wins. Takes
effect once the agent wires manifest reaping defaults into target
admission.
@JeroenSoeters

Copy link
Copy Markdown
Contributor Author

Superseded: the reaping default is moving out of the plugin manifest (which is package metadata) onto a class-level annotation on the target Config class, next to the ConfigFieldHint mutability annotations — it rides ConfigSchema to admission with no agent-side manifest read. The manifest field is being removed from formae core in the rework of platform-engineering-labs/formae#756; the annotation replacement lands once the core release carrying formae.ConfigHint is published and this plugin's schema pin moves to it.

@JeroenSoeters
JeroenSoeters deleted the chore/never-reap-manifest branch September 4, 2026 03:11
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.

1 participant