← Back to issue list

Need a way to delete account-keys from snapcraft integration tests

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1621441
Type
issue
State
open
Author
~elopio
Labels
—
Created
Updated
Closed
—

Current evaluation

Account-key deletion remains unimplemented, limiting repeatable non-fake-store integration testing; the current client supports registration but exposes no delete path.

Suggested action: needs triage

Reason: The body cites snapcore/snapcraft#726 and says its account-key test is disabled for non-fake stores because a key can only be registered once; current source confirms register_key exists but no deletion path. With no labels, assignee, or substantive maintainer response, and two possible approaches still proposed, the issue still needs maintainer triage rather than closure.

Evaluated by: mr-cal-bot

Impact: 40 Quick Win: 10 Complexity: 58 Confidence: 90 Actionability: 62

Issue body

https://github.com/snapcore/snapcraft/pull/726 adds an integration test that creates account-keys on the store. It's currently disabled for non-fake stores because it would only ever be able to register any given key once. We need a way to disable account-keys, and the integration test should really do both once we have that capability. However, we should perhaps also generate a fresh key for each integration test run and register that. If we do that, then we need a job that periodically clears out the test account-keys from our assertions database.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 40
Quick Win: 10
Complexity: 58
Confidence: 90
Actionability: 62
needs triage Account-key deletion remains unimplemented, limiting repeatable non-fake-store integration testing; the current client supports registration but exposes no delete path.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 11
Complexity: 55
Confidence: 89
Actionability: 62
keep open Account keys still lack a deletion path for repeatable real-store integration tests; the current store client supports registration only.
qwen/qwen3.6-35b-a3b
Impact: 25
Quick Win: 9
Complexity: 40
Confidence: 70
Actionability: 60
needs triage Feature request to add a delete-key command for managing account-keys in integration tests. Issue is unlabelled with no maintainer response after 10 years.
qwen/qwen3.8-27b
Impact: 25
Quick Win: 11
Staleness: 95
Complexity: 55
Confidence: 70
Support Request: 10
needs triage Request for a way to delete/disable store account-keys so the register-key integration test (added in PR #726) can run against real stores with fresh keys per run. Open since 2019, no labels, no comments, no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 90
Support Request: 10
close stale Request to implement account-key deletion and cleanup for snapcraft integration tests to enable fresh key generation per run. Issue has been inactive for nearly 10 years with no maintainer response or labels.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 30
Confidence: 95
Support Request: 10
close stale Request to implement account-key deletion and cleanup for integration tests to enable fresh key generation per run. Unaddressed for nearly 10 years with zero maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 10
close stale Request for a mechanism to delete or disable account-keys in snapcraft integration tests to allow safe test runs and periodic cleanup of test assertions. No maintainer response or activity in ~10 years.

Update history

Date Change
created

Related work

  • Related To: snapcore/snapcraft#726 (confidence 99%)

    The referenced pull request added the account-key integration test that is disabled for non-fake stores.

Related issues

No related issues found above the similarity threshold.