← Back to issue list

Allow strict fetch-service sessions on the command-line

View original Github issue

Metadata

Project
craft-application
Number
#487
Type
issue
State
closed
Author
tigarmo
Labels
Created
Updated
Closed

Current evaluation

Closed after UX discussion for --use-fetch-service=strict and --use-fetch-service=permissive CLI flags. No implementation or PR was created, indicating the feature was abandoned or deferred.

Suggested action:

No scores available.

Issue body

### What needs to get done The command line UI to enable the fetch-service should allow enabling strict or permissive sessions. Details TBD ### Why it needs to get done When running locally one can use permissive sessions during development, and strict sessions to verify the artifact builds as expected.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed after UX discussion for --use-fetch-service=strict and --use-fetch-service=permissive CLI flags. No implementation or PR was created, indicating the feature was abandoned or deferred.
qwen/qwen3.6-35b-a3b Closed and abandoned externally, tracked internally as CRAFT-3435. CLI UX defined as --use-fetch-service=strict|permissive with a mandatory parameter. No merge or fix provided.
qwen3.6-35b-a3b-mtp-q6 Closed and abandoned after UX design was finalized and an internal Jira ticket was created. No code changes or pull requests were submitted, leaving the proposed CLI flags unmerged.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#490 feat: allow strict/permissive fetch-service sessions craft-application merged Merged after approval and CI checks, adding mandatory strict or permissive session arguments to the --use-fetch-service flag. Resolves issue #487.
80%
#488 Hide the fetch-service command line option, and warn it's experimental craft-application closed Closed without implementation or resolution details. An internal Jira ticket was created, but no code changes or merge information were provided, indicating the request was likely deferred or abandoned.
71%