repoconfig

type ArgSpec struct {
	Name string `yaml:"name"`
	Req  bool   `yaml:"required"`
	Desc string `yaml:"description"`
}

type C struct {
	DefaultJob string          `yaml:"defaultJob"`
	Rules      []*JobStartRule `yaml:"rules"`
}

type JobSpec struct {
	// Desc describes the purpose of this job spec.
	Desc string `yaml:"description,omitempty"`

	// Pod is the actual job spec to start. Prior to deploying this to Kubernetes, we'll run this
	// as a Go template.
	Pod *corev1.PodSpec `yaml:"pod"`

	// Mutex makes job execution exclusive, with new ones canceling the currently running one.
	// For example: job A is running at the moment, and job B is about to start. If A and B share the
	// same mutex, B will cancel A.
	Mutex string `yaml:"mutex,omitempty"`

	// Args describe annotations which this job expects. This list is only used on the UI when manually
	// starting the job.
	// This is list is neither exhaustive (i.e. jobs can use annotations not listed here), nor binding
	// (i.e. jobs can run even when annotations listed here are not present). What matters for a job to
	// run is only if Kubernetes accepts the produced podspec.
	Args []ArgSpec `yaml:"args,omitempty"`

	// Sidecars list side car containers of the job, i.e. containers
	// for which we don't wait that they end to end the job.
	Sidecars []string `yaml:"sidecars,omitempty"`

	// Plugins list plugin-specific information
	Plugins map[string]string `yaml:"plugins,omitempty"`
}

type JobStartRule struct {
	Path string                      `yaml:"path"`
	Expr []*werftv1.FilterExpression `yaml:"matchesAll"`
}

type JobStartRuleOr struct {
	Or []string `yaml:"or"`
}