engine: Don't force validation for hidden resources
I think this is what I want in most scenarios, is there a reason to do otherwise? This is because we may wish to export incomplete resources, where the remaining necessary fields for validation happens on collect.
This commit is contained in:
@@ -154,7 +154,8 @@ type MetaParams struct {
|
||||
// named resources. It can even be used as part of an edge or via a
|
||||
// send/recv receiver. It can NOT be a sending vertex. These properties
|
||||
// differentiate the use of this instead of simply wrapping a resource
|
||||
// in an "if" statement.
|
||||
// in an "if" statement. If it is hidden, then it does not need to pass
|
||||
// the resource Validate method step.
|
||||
Hidden bool `yaml:"hidden"`
|
||||
|
||||
// Export is a list of hostnames (and/or the special "*" entry) which if
|
||||
|
||||
Reference in New Issue
Block a user