← Back to issue list

Custom compatibility tags in the provider service

View original Github issue

Metadata

Project
craft-application
Number
#105
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Feature request to add a per-app compatibility tag addendum to AppMetadata so downstream apps like charmcraft need not override ProviderService.get_base. Unlabelled, no maintainer activity since 2024-03; feature still unimplemented in current code.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and its only comment is the autogenerated Jira-sync bot message (2024-03-12), so it has never been categorised or prioritised despite being filed by a maintainer. The request remains valid — ProviderService.compatibility_tag is still hardcoded to '.1' (provider.py:97-99) and AppMetadata has no such field — but it needs a maintainer to decide scope and priority.

Impact: 35 Quick Win: 22.75 Staleness: 72 Complexity: 35 Confidence: 80 Support Request: 10

Issue body

### What needs to get done Take an integer value (in `AppMetadata`?) that provides a per-application addendum to the craft-providers compatibility tag, defaulting to zero. Set the `compatibility_tag` keyword argument for the provider base to include that value. ### Why it needs to get done Charmcraft has to override `ProviderService` and `get_base` because it adds custom compatibility tags: https://github.com/canonical/charmcraft/pull/1330/files/84ffcdd7a0731a17fcae83a889ed7e2143f7cfb6#diff-a32511469d8ae4dd52bf0ce115517e3cc980f46568ae386be734af9f2978b7c7 This shouldn't be necessary.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 22.75
Staleness: 72
Complexity: 35
Confidence: 80
Support Request: 10
needs triage Feature request to add a per-app compatibility tag addendum to AppMetadata so downstream apps like charmcraft need not override ProviderService.get_base. Unlabelled, no maintainer activity since 2024-03; feature still unimplemented in current code.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 20
Confidence: 75
Support Request: 10
needs triage Feature request to allow custom compatibility tags in the provider service, eliminating the need for charmcraft to override internal classes. Currently unlabelled and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Feature request to pass a custom compatibility tag integer to the provider service, avoiding Charmcraft overrides. Unlabelled, unassessed, and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 30
Confidence: 70
Support Request: 10
close stale Implement an integer addendum in AppMetadata to customize provider compatibility tags, removing the need for Charmcraft to override ProviderService. Open and unassigned, synced to Jira CRAFT-2606, last activity 389 days ago.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#1330 (confidence 85%)

    Explicitly cited in the issue body as the charmcraft workaround (overriding ProviderService/get_base for custom compatibility tags) that this feature would eliminate.

Related issues

No related issues found above the similarity threshold.