docs/spec
Christie Wilson 07c926d956 Update condition `type` in spec and do not assert against `reason` (#903)
* Some spec docs were using `RolloutComplete` for the condition type,
  however as errors.md documents and as discussed in #351, the type
  should actually be `Ready`
* The conformance tests were asserting against the condition `Reason`
  but as per #351 and errors.md, values in this field are for the
  user to consume and should be transpart to client applications.
* errors.md didn't make the latter as clear as mattmoor@'s comment
  in #351 so I copied some of his comment into the doc

Also reorganized some of errors.md to make it easier to identify,
by field, what requirements are.
2018-05-29 17:40:10 -07:00
..
images Service docs (#685) 2018-05-07 10:59:23 -07:00
README.md Add docs re. keeping spec/implementation/conformance tests in sync (#781) 2018-05-03 10:32:20 +02:00
errors.md Update condition `type` in spec and do not assert against `reason` (#903) 2018-05-29 17:40:10 -07:00
motivation.md Add docs re. keeping spec/implementation/conformance tests in sync (#781) 2018-05-03 10:32:20 +02:00
normative_examples.md Update condition `type` in spec and do not assert against `reason` (#903) 2018-05-29 17:40:10 -07:00
overview.md Service docs (#685) 2018-05-07 10:59:23 -07:00
spec.md Update condition `type` in spec and do not assert against `reason` (#903) 2018-05-29 17:40:10 -07:00

README.md

Elafros API spec

This directory contains the specification of the Elafros API, which is implemented in pkg/apis/ela/v1alpha1 and verified via the conformance tests.

Updates to this spec should include a corresponding change to the API implementation and the conformance tests. (#780)

Docs in this directory: