Skip to content

Validate Channel CRD specs as early and thoroughly as possible.  #1349

@vaikas

Description

@vaikas

Problem
As discussed here:
#1239 (comment)

It would be great to validate Template Spec for Channel CRDs as early as possible. This would involve fetching the underlying CRD and using the openapi schema to do validation. Note that this may not be comprehensive, as some of them might do more complicated validation as well, but might be a start. Also, I suppose using something like APIServer dryrun might be a better solution?
https://kubernetes.io/docs/reference/using-api/api-concepts/#dry-run

Persona:
Developers

Exit Criteria
When broker / pipeline (and others that take Channel CRD templates as their arguments) are validated during the creation of the actual object.

Time Estimate (optional):

Additional context (optional)
Add any other context about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apikind/feature-requestlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions