← Back to issue list

Allow additionalProperties under "parts/plugin" in rockcraft schema

View original Github issue

Metadata

Project
rockcraft
Number
#471
Type
pull request
State
merged
Author
linostar
Labels
Created
Updated
Closed

Current evaluation

Merged. Updates the Rockcraft schema to allow additional properties under the plugin field, preventing false validation errors for valid configurations. Validation is deferred to Rockcraft. Approved by two reviewers and merged following schema regeneration.

Suggested action:

No scores available.

Issue body

- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? ----- ## Description Currently, Rockcraft schema doesn't allow additional fields under `plugin`, a field under `parts`. There are different values that can be used for `plugin`, and for each value, there is a different set of plugin properties that can be used under that plugin. The current schema generator, using pydantic's schema function, can't crawl the subclassed PluginProperties models in order to include their respective plugin properties and whitelist them. With the current `additionalProperties` setting of the `plugin` field set to `false`, Rockcraft schema may consider a `rockcraft.yaml` invalid when its syntax is actually correct. In order to avoid that, we are going to whitelist all additional properties under `plugin`, even if it means whitelisting incorrect properties too, letting rockcraft be the final judge of them.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged. Updates the Rockcraft schema to allow additional properties under the plugin field, preventing false validation errors for valid configurations. Validation is deferred to Rockcraft. Approved by two reviewers and merged following schema regeneration.
qwen3.6-35b-a3b-mtp-q6 Merged schema update allowing additionalProperties under the plugin field. This prevents false validation errors for valid rockcraft.yaml files by whitelisting plugin properties and deferring final checks to the application. Rebased and regenerated schema before merge.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1057 fix(schema): allow extensions field in rockcraft.yaml rockcraft merged Merged a schema-only update adding the extensions field to rockcraft.yaml, resolving IDE validation error #922. Approved by two reviewers, rebased on main, and merged without runtime impact.
76%
#460 Move Permissions definition in rockcraft schema to top scope rockcraft merged Merged a fix relocating the Permissions definition in rockcraft's schema.json to the top-level scope, correcting validation errors. Approved by two reviewers, passed CI, and integrated. A follow-up PR will implement automated schema validation.
72%