Action parameters and config options represent integers in two different ways (`int` vs `integer`) in charmcraft.yaml

Metadata

Project: charmcraft
Number: #2067
Type: issue
State: open
Author: gruyaume
Labels: —
Created: 2025-01-07 05:27 PM UTC
Updated: 2025-08-15 03:17 PM UTC
Closed: —

Current evaluation

charmcraft.yaml uses 'int' for config options but 'integer' for action params. Maintainer confirmed this mirrors Juju's config.yaml/actions.yaml and reported the change to Juju (juju/juju#19979). Blocked on Juju accepting 'integer' in config.yaml.

Suggested action: keep open

Reason: Maintainer @lengau acknowledged the issue on 2025-06-13, explaining the values are tied to Juju's config.yaml and actions.yaml formats, and filed juju/juju#19979 requesting Juju accept 'integer' in config.yaml. The issue is triaged, valid, and explicitly blocked on an external dependency (Juju), so it should remain open until that upstream change lands.

Impact: 25 Quick Win: 13.75 Staleness: 55 Complexity: 45 Confidence: 82 Support Request: 10

Issue body

### What needs to get done ## Description Action parameters and config options represent integers in two different ways in charmcraft.yaml. Configuration option accept the type `int`, while action parameters accept the type `integer`. We're talking about the same concept here, there is no good reason to have two ways of talking about integers. ## Reference ```charmcraft.yaml ... config: options: subscriber-count: type: int default: 1 description: Number of subscribers to simulate actions: my-action: description: Run my action params: timeout: type: integer description: Time to wait for the simulation to complete (in seconds). The more subscribers, the longer the simulation will take. default: 300 ``` ### Why it needs to get done The same concept is represented in two different ways, unnecessarily confusing users.

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 12:17 AM UTC	qwen/qwen3.8-27b	Impact: 25 Quick Win: 13.75 Staleness: 55 Complexity: 45 Confidence: 82 Support Request: 10	keep open	charmcraft.yaml uses 'int' for config options but 'integer' for action params. Maintainer confirmed this mirrors Juju's config.yaml/actions.yaml and reported the change to Juju (juju/juju#19979). Blocked on Juju accepting 'integer' in config.yaml.
2026-07-22 12:38 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 70 Complexity: 15 Confidence: 85 Support Request: 10	keep open	Inconsistency between int and integer types in charmcraft.yaml config vs actions. Maintainer acknowledged it is tied to Juju upstream and reported the change there; currently waiting on Juju.
2026-07-07 08:56 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 80 Complexity: 15 Confidence: 90 Support Request: 5	keep open	Inconsistency between config.options using int and actions.params using integer in charmcraft.yaml. Acknowledged by maintainers but blocked on upstream Juju changes to unify the type names.
2026-07-05 02:45 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 75 Complexity: 35 Confidence: 90 Support Request: 0	keep open	Inconsistency between config.options using int and actions.params using integer in charmcraft.yaml. Maintainer notes it is dictated by Juju upstream and has been reported there. Awaiting upstream resolution.
2026-06-15 10:23 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 65 Complexity: 20 Confidence: 90 Support Request: 0	keep open	Inconsistent integer type naming between charmcraft config options (int) and action parameters (integer). Blocked by Juju schema. Upstream fix requested to standardize on integer. Awaiting upstream resolution.

Update history

No update history recorded yet.

Related work

Blocked By: juju/juju#19979 (confidence 90%)
Maintainer explicitly stated they reported this to Juju and are waiting for Juju to accept 'integer' in config.yaml before charmcraft can unify the type names.

Related issues

No related issues found above the similarity threshold.