Add enum values generation to documentation (#3404) (#207)

* Add enum values generation to documentation, remove previous handwritten lists unless they add value

* Add possible enum values to inspec doc generation

* Add default, possible values to the schema description

* Format fixes

* Try spacing to see how md looks

* PR feedback

* Order of operations

* Bigger spacefor markdown

Signed-off-by: Modular Magician <magic-modules@google.com>
This commit is contained in:
The Magician 2020-04-24 13:45:23 -04:00 committed by GitHub
commit 282f8e3b82
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
40 changed files with 114 additions and 189 deletions

View file

@ -356,8 +356,7 @@ resources:
description:
- Indicates whether the backend service will be used with internal or external
load balancing. A backend service created for one type of load balancing cannot
be used with the other. Must be `EXTERNAL` or `INTERNAL_SELF_MANAGED` for
a global backend service. Defaults to `EXTERNAL`.
be used with the other.
returned: success
type: str
name:
@ -379,9 +378,8 @@ resources:
protocol:
description:
- The protocol this BackendService uses to communicate with backends.
- 'Possible values are HTTP, HTTPS, HTTP2, TCP, and SSL. The default is HTTP.
**NOTE**: HTTP2 is only valid for beta HTTP/2 load balancer types and may
result in errors if used with the GA API.'
- 'The default is HTTP. **NOTE**: HTTP2 is only valid for beta HTTP/2 load balancer
types and may result in errors if used with the GA API.'
returned: success
type: str
securityPolicy: