New issue
Advanced search Search tips

Issue 821053 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Decide how to handle sub-models in yaml

Project Member Reported by sjg@chromium.org, Mar 12 2018

Issue description

The current schema supports sub-models, where most things can be overridden at that level. With yaml this is not implemented. Some models in Coral use sub-models, so this may need to be addressed. Alternatively, perhaps the concept of a 'project' would obviate this need, and people would then happily use separate models for each sub-model.

 
Components: -Infra>Client>Chrome
mentioned offline: I'm not sure what the right component for these issues is, but it's not I>C>C.
yaml already solves this because submodels will just be blown out
Status: Fixed (was: Untriaged)

Sign in to add a comment