Packages

p

nelson

yaml

package yaml

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. All

Type Members

  1. class AlertingYaml extends AnyRef
  2. class BackendDestinationParser extends JavaTokenParsers
  3. class ClusterYaml extends AnyRef
  4. class ConstraintYaml extends AnyRef
  5. class DatacenterTargetYaml extends AnyRef
  6. class DependencyYaml extends AnyRef
  7. class GroupByYaml extends AnyRef
  8. class HealthCheckYaml extends AnyRef
  9. class InstancesYaml extends AnyRef
  10. class LikeYaml extends AnyRef
  11. class LoadbalancerYaml extends AnyRef
  12. class ManifestYaml extends AnyRef
  13. class NamespaceLoadbalancerYaml extends AnyRef
  14. class NamespaceUnitYaml extends AnyRef
  15. class NamespaceYaml extends AnyRef
  16. class NotificationEmailYaml extends AnyRef
  17. class NotificationSlackYaml extends AnyRef
  18. class NotificationYaml extends AnyRef
  19. class PlanResourceYaml extends AnyRef
  20. class PlanYaml extends AnyRef
  21. class PortParser extends JavaTokenParsers
  22. class PrometheusAlertYaml extends AnyRef
  23. class PrometheusConfigYaml extends AnyRef
  24. class PrometheusRuleYaml extends AnyRef
  25. class ResourceYaml extends AnyRef
  26. class RouteYaml extends AnyRef
  27. class TrafficShiftYaml extends AnyRef
  28. class UnitYaml extends AnyRef

    Ok this is a bit janky: 'required' fields should have their value initially set to '_' whilst fields that are "optional" should have their value set to a sane default, such as an empty list in the case of lists.

  29. class VolumeYaml extends AnyRef
  30. class WorkflowYaml extends AnyRef

Value Members

  1. object BackendDestinationParser
  2. object ManifestParser extends YamlParser[Manifest]
  3. object ManifestV1Parser
  4. object PortParser

    This parser expects the following syntax to be used when serialising port definitions - all elements are required.

    This parser expects the following syntax to be used when serialising port definitions - all elements are required.

    name->port/protocol

    Where the elements specifically are:

    * name: represents the logical 'name' or 'reference' you want to use this port for. Examples would be 'default' for the default service port, 'monitoring' for the monitoring port, or something like 'mutualtls' for a secure channel. The actual name is not important, but being a short, obvious reference to what it served on that particular port is typically useful.

    * port: the actual port number the container binds too when exposing network functionaltiy. It goes without saying that the number must be between 1 and 65535 to form a valid, usable port definition.

    * protocol: the protocol used by the service being exposed by this port. This param is used by nelson to know what should be done to the routing tables.

    Here are some examples of usage, that are valid and accepted by this parser:

    default->9080/https monitoring->4444/tcp

Ungrouped