microsoft / microsoft/trident

COSI: After relaxing metadata parsing, servicing operations should make more of an effort to ensure the COSI file is acceptable

Open
#428 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
32
Forks
18
Avg merge
1d 17h
Merged PRs (30d)
31

Description

> I see, do we do more strict validation/returning errors once we know whether trident is doing `stream image` or something else?

_Originally posted by @ayaegashi in https://github.com/microsoft/trident/pull/394#discussion_r2636465398_

Contributor guide

Open the contributing guide

Research direction

Start by locating the COSI metadata parsing and servicing-operation paths, then determine how the `stream image` operation is distinguished from other operations. Define the acceptable COSI-file checks for each path and verify that invalid metadata produces the intended result.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.