* * This will take a buffer of bytes that encode a YAML object definition (potentially multi-doc) * and will return one or many (in the case of multiple objects) metav1Objects * This is an interface defined in meta/v1 and it's probably the most convenient to use.

copied from https://github.com/instrumenta/kubeval/blob/9c9c0a5b3cc619dbd94129af77c8512bfd0f1763/kubeval/utils.go#L24.

* * For each object (in the order that they occur in the yaml file), tell me what line number the object starts on.

main function that performs the linting.

* * Create a new RuleSorter given a list of rules * Usual use case is to use the RuleSorter to access the rules in the correct order! **/.

container tests.

cronjob tests.

deployment specific tests.

interdependent rules.

job rules.

namespace rules.

network policy rules.

pod spec rules.

service rules.

Captures metadata when parsing yaml objects from text files.

Represents a Linter Rule.

This object is used to store all the rules belonging to a resource group and looks like: &rulesorter.RuleSorter{ rules:24:(*lint.Rule)(0xc00039caf0), edges:24:map[lint.RuleID]lint.RuleID{} } */.

I'm defining an enum for all the test IDs so we know at compile time whether we're trying to access a non-existent test.