bases: introduce persistent in-instance datastore InstanceConfig
Metadata
Current evaluation
Merged #19 via dc82c81, adding persistent in-instance configuration, compatibility-tag tracking, BaseConfigurationError, and pydantic.
Resolution: closed resolved
Reason: Pull request #19 was approved and merged into the project; history records merge commit dc82c81 and implementation commit e9e5f43. Its stated prerequisite, #18, had also been merged.
Evaluated by: mr-cal-bot
No scores available.
Issue body
bases: introduce persistent in-instance datastore InstanceConfig
Enable Bases to persist a datastore that they can load on future use.
Initially, the only usage of this datastore is to track a "compatibility
tag", a simple mechanism in which a Base can ensure the instance to be
re-used is compatibile with the current Base.
- Add generic BaseConfigurationError() which will be used for base
configuration errors.
- Update requirements to add pydantic.
Signed-off-by: Chris Patterson <chris.patterson@canonical.com>
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #19 via dc82c81, adding persistent in-instance configuration, compatibility-tag tracking, BaseConfigurationError, and pydantic. | |
| qwen/qwen3.6-35b-a3b | — | closed resolved | Merged PR introducing InstanceConfig to persist a datastore for Bases, initially tracking a compatibility tag. Adds BaseConfigurationError and updates requirements to include pydantic. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
canonical/craft-providers#18
(confidence 100%)
PR #19 explicitly depended on #18, which introduced the abstract Base.
Related issues
No related issues found above the similarity threshold.