Repository navigation
Resolve silently ignored rm_folders.description input #82
Description
Problem
The root input accepts rm_folders[*].description, but the governance module's folder object has no description attribute and the resource does not receive it. Users can supply a description that has no effect.
Verified on main at 2bb7c755692674ad619ffc46a0a17a781f019106 by source inspection:
- Root input accepts
description = optional(string, null). - Governance module type omits the field.
- Folder resource uses name, parent and owner only.
Reproduction
Add a description to an otherwise valid rm_folders entry and trace the input through the governance module. It is discarded at the module boundary. No cloud apply is needed to establish this loss.
Acceptance criteria
- If supported by the provider/API, wire the description through and add a test.
- Otherwise document the limitation and explicitly reject or deprecate the unsupported input with a compatibility path.
- Root/module types, examples and generated docs agree.
- A regression test prevents accepting a populated description while silently ignoring it.
The Configurator should not offer an apparently functional description field until this contract is resolved. This is separate from folder deletion (#22).
Activity
lweberru commentedon Oct 10, 2026
Local qualification update — 2026-10-10 (#82)
Reviewed STACKIT provider 0.114.0 schema has no folder description attribute. Root and direct Governance module now explicitly reject meaningful rm_folders description values instead of silently discarding them. Omitted/null/empty/whitespace-only values remain compatible. The child object retains the optional field to validate it. Generated root/governance READMEs and current input inventories reflect the contract; the existing editor already hides the unsupported field and states the limitation.
Evidence: negative root/direct-module cases and direct null/empty/whitespace compatibility included in 14 passing credential-free native cases; provider-schema assertion, fmt/init/validate; deterministic inventory freshness; app lint/types/build, 436 unit passes (53 gated skips), 278 browser passes.
The rejection of previously ignored meaningful values is intentional. Future provider description support requires requalification. Local-only, not released; issue remains open. No Cloud/State operations or historical binding changes.
lweberru commentedon Oct 16, 2026
Implemented in #102. The reviewed provider does not support folder descriptions, so both the root and direct governance-module contracts explicitly reject populated descriptions instead of silently discarding them. Omitted, null, empty and whitespace-only values retain compatibility; the Configurator uses the same boundary and does not advertise functional folder descriptions.
The native Standalone suite passed all 11 cases, including root/direct-module rejection and empty/null compatibility. Full native and catalogue checks are green in the integration PR. This issue is linked for automatic closure when that PR merges; no cloud Apply is needed to establish the input-contract fix.