← Back to issue list

allow user configuration of the Pebble entrypoint binary

View original Github issue

Metadata

Project
rockcraft
Number
#65
Type
issue
State
open
Author
cjdcordeiro
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to let users configure the Pebble entrypoint snap channel/version and set a policy for user-supplied Pebble layers. Triaged 2026-02-26 as still valid; channel still hardcoded to pebble/latest/stable, no PR proposed.

Suggested action: keep open

Reason: A maintainer (gcomneno) triaged this on 2026-02-26 and explicitly confirmed it 'still seems valid as a feature request,' documenting that rockcraft/pebble.py:368 still hardcodes stage-snaps to pebble/latest/stable and that define_pebble_layer() has no policy for user-supplied layers. It is a scoped, acknowledged feature request with no proposed PR, so it should remain open rather than be closed as stale.

Impact: 45 Quick Win: 18.0 Staleness: 50 Complexity: 60 Confidence: 85 Support Request: 10

Issue body

Users can define the Pebble services to be executed, but they should also be able to configure certain parameters about the Pebble software which is being installed in the ROCK. The most obvious parameter is the Pebble version, i.e., users should be able to have a say on the version of Pebble that is being used as the ROCK entrypoint. See https://github.com/canonical/rockcraft/pull/59#discussion_r954192413 for more details --- edit: Additionally, Rockcraft should know how to handle (check/support/deny) the user definitions of custom Pebble layers. Example: the user defines the PEBBLE_LAYERS_PATH and inner layer files within a custom part, conflicting with the rockcraft-defined base Pebble layer from the `services` field (see related discussion in https://github.com/canonical/rockcraft/pull/205#discussion_r1154090694)

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 45
Quick Win: 18.0
Staleness: 50
Complexity: 60
Confidence: 85
Support Request: 10
keep open Feature request to let users configure the Pebble entrypoint snap channel/version and set a policy for user-supplied Pebble layers. Triaged 2026-02-26 as still valid; channel still hardcoded to pebble/latest/stable, no PR proposed.
qwen/qwen3.6-35b-a3b
Staleness: 50
Complexity: 65
Confidence: 85
Support Request: 10
keep open Request to allow configurable Pebble version/channel and define policies for user-supplied Pebble layers in Rockcraft. Recently triaged and confirmed valid, but no implementation or PR exists yet.
qwen3.6-35b-a3b-mtp-q6
Staleness: 45
Complexity: 65
Confidence: 85
Support Request: 10
needs triage Feature request to allow configurable Pebble version and layer handling in Rockcraft. Currently hardcoded to latest/stable. Validated as still relevant, but lacks implementation or official prioritization.
qwen3.6-35b-a3b-mtp-q6
Staleness: 55
Complexity: 50
Confidence: 75
Support Request: 10
needs triage Allow users to configure the Pebble entrypoint version and define validation policies for custom Pebble layers in Rockcraft. Currently hardcoded to latest stable. No PR exists; implementation pending.

Update history

No update history recorded yet.

Related work

  • Related To: rockcraft#59 (confidence 80%)

    PR referenced in the body for the original Pebble-version parameter discussion; context for the feature request.

  • Related To: rockcraft#205 (confidence 80%)

    PR referenced for the user-defined Pebble layers / PEBBLE_LAYERS_PATH conflict discussion.

  • Related To: rockcraft#1214 (confidence 75%)

    Only current channel variation: auto-selects pebble/fips/stable for FIPS pro services, not user-configurable from rockcraft.yaml.

Related issues

No related issues found above the similarity threshold.