Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Cloud Scheduler Job #203

Merged
merged 4 commits into from
Nov 6, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
97 changes: 97 additions & 0 deletions docs/resources/google_cloud_scheduler_job.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
---
title: About the google_cloud_scheduler_job resource
platform: gcp
---

## Syntax
A `google_cloud_scheduler_job` is used to test a Google Job resource

## Examples
```
describe google_cloud_scheduler_job(project: 'chef-gcp-inspec', region: us-central1, name: 'job-name') do
it { should exist }

its('description') { should cmp 'A description' }
its('schedule') { should cmp '*/8 * * * *' }
its('time_zone') { should cmp 'America/New_York' }
its('http_target.http_method') { should cmp 'POST' }
its('http_target.uri') { should cmp 'https://example.com/ping' }
end
```

## Properties
Properties that can be accessed from the `google_cloud_scheduler_job` resource:


* `name`: The name of the job.

* `description`: A human-readable description for the job. This string must not contain more than 500 characters.

* `schedule`: Describes the schedule on which the job will be executed.

* `time_zone`: Specifies the time zone to be used in interpreting schedule. The value of this field must be a time zone name from the tz database.

* `retry_config`: By default, if a job does not complete successfully, meaning that an acknowledgement is not received from the handler, then it will be retried with exponential backoff according to the settings

* `retry_count`: The number of attempts that the system will make to run a job using the exponential backoff procedure described by maxDoublings. Values greater than 5 and negative values are not allowed.

* `max_retry_duration`: The time limit for retrying a failed job, measured from time when an execution was first attempted. If specified with retryCount, the job will be retried until both limits are reached. A duration in seconds with up to nine fractional digits, terminated by 's'.

* `min_backoff_duration`: The minimum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

* `max_backoff_duration`: The maximum amount of time to wait before retrying a job after it fails. A duration in seconds with up to nine fractional digits, terminated by 's'.

* `max_doublings`: The time between retries will double maxDoublings times. A job's retry interval starts at minBackoffDuration, then doubles maxDoublings times, then increases linearly, and finally retries retries at intervals of maxBackoffDuration up to retryCount times.

* `pubsub_target`: Pub/Sub target If the job providers a Pub/Sub target the cron will publish a message to the provided topic

* `topic_name`: The name of the Cloud Pub/Sub topic to which messages will be published when a job is delivered. The topic name must be in the same format as required by PubSub's PublishRequest.name, for example projects/PROJECT_ID/topics/TOPIC_ID.

* `data`: The message payload for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

* `attributes`: Attributes for PubsubMessage. Pubsub message must contain either non-empty data, or at least one attribute.

* `app_engine_http_target`: App Engine HTTP target. If the job providers a App Engine HTTP target the cron will send a request to the service instance

* `http_method`: Which HTTP method to use for the request.

* `app_engine_routing`: App Engine Routing setting for the job.

* `service`: App service. By default, the job is sent to the service which is the default service when the job is attempted.

* `version`: App version. By default, the job is sent to the version which is the default version when the job is attempted.

* `instance`: App instance. By default, the job is sent to an instance which is available when the job is attempted.

* `relative_uri`: The relative URI. The relative URL must begin with "/" and must be a valid HTTP relative URL. It can contain a path, query string arguments, and \# fragments. If the relative URL is empty, then the root path "/" will be used. No spaces are allowed, and the maximum length allowed is 2083 characters

* `body`: HTTP request body. A request body is allowed only if the HTTP method is POST or PUT. It will result in invalid argument error to set a body on a job with an incompatible HttpMethod.

* `headers`: HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created.

* `http_target`: HTTP target. If the job providers a http_target the cron will send a request to the targeted url

* `uri`: The full URI path that the request will be sent to.

* `http_method`: Which HTTP method to use for the request.

* `body`: HTTP request body. A request body is allowed only if the HTTP method is POST, PUT, or PATCH. It is an error to set body on a job with an incompatible HttpMethod.

* `headers`: This map contains the header field names and values. Repeated headers are not supported, but a header value can contain commas.

* `oauth_token`: Contains information needed for generating an OAuth token. This type of authorization should be used when sending requests to a GCP endpoint.

* `service_account_email`: Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

* `scope`: OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.

* `oidc_token`: Contains information needed for generating an OpenID Connect token. This type of authorization should be used when sending requests to third party endpoints or Cloud Run.

* `service_account_email`: Service account email to be used for generating OAuth token. The service account must be within the same project as the job.

* `audience`: Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.

* `region`: Region where the scheduler job resides


## GCP Permissions
42 changes: 42 additions & 0 deletions docs/resources/google_cloud_scheduler_jobs.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
title: About the google_cloud_scheduler_jobs resource
platform: gcp
---

## Syntax
A `google_cloud_scheduler_jobs` is used to test a Google Job resource

## Examples
```
google_cloud_scheduler_jobs(project: 'chef-gcp-inspec', region: ).names.each do |name|
describe google_cloud_scheduler_job(project: 'chef-gcp-inspec', region: us-central1, name: name) do
it { should exist }

its('description') { should cmp 'A description' }
its('schedule') { should cmp '*/8 * * * *' }
its('time_zone') { should cmp 'America/New_York' }
its('http_target.http_method') { should cmp 'POST' }
its('http_target.uri') { should cmp 'https://example.com/ping' }
end
end
```

## Properties
Properties that can be accessed from the `google_cloud_scheduler_jobs` resource:

See [google_cloud_scheduler_job.md](google_cloud_scheduler_job.md) for more detailed information
* `names`: an array of `google_cloud_scheduler_job` name
* `descriptions`: an array of `google_cloud_scheduler_job` description
* `schedules`: an array of `google_cloud_scheduler_job` schedule
* `time_zones`: an array of `google_cloud_scheduler_job` time_zone
* `retry_configs`: an array of `google_cloud_scheduler_job` retry_config
* `pubsub_targets`: an array of `google_cloud_scheduler_job` pubsub_target
* `app_engine_http_targets`: an array of `google_cloud_scheduler_job` app_engine_http_target
* `http_targets`: an array of `google_cloud_scheduler_job` http_target
* `regions`: an array of `google_cloud_scheduler_job` region

## Filter Criteria
This resource supports all of the above properties as filter criteria, which can be used
with `where` as a block or a method.

## GCP Permissions
2 changes: 1 addition & 1 deletion docs/resources/google_compute_backend_service.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ Properties that can be accessed from the `google_compute_backend_service` resour

* `description`: An optional description of this resource. Provide this property when you create the resource.

* `group`: The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend service can not contain mix of Instance Group and Network Endpoint Group backends. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.
* `group`: The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.

* `max_connections`: The max number of simultaneous connections for the group. Can be used with either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or one of maxConnectionsPerInstance or maxConnectionsPerEndpoint, as appropriate for group type, must be set.

Expand Down
44 changes: 33 additions & 11 deletions docs/resources/google_compute_region_backend_service.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,33 +24,55 @@ end
Properties that can be accessed from the `google_compute_region_backend_service` resource:


* `name`: Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
* `backends`: The set of backends that serve this RegionBackendService.

* `health_checks`: The list of HealthChecks for checking the health of the backend service. Currently at most one health check can be specified, and a health check is required.
* `balancing_mode`: Specifies the balancing mode for this backend. Defaults to CONNECTION.

* `backends`: The list of backends that serve this RegionBackendService.
* `capacity_scaler`: A multiplier applied to the group's maximum servicing capacity (based on UTILIZATION, RATE or CONNECTION). A setting of 0 means the group is completely drained, offering 0% of its available Capacity. Valid range is [0.0,1.0].

* `description`: An optional description of this resource. Provide this property when you create the resource.

* `group`: The fully-qualified URL of an Instance Group. This defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. Note that you must specify an Instance Group resource using the fully-qualified URL, rather than a partial URL. The instance group must be within the same region as the BackendService.
* `group`: The fully-qualified URL of an Instance Group or Network Endpoint Group resource. In case of instance group this defines the list of instances that serve traffic. Member virtual machine instances from each instance group must live in the same zone as the instance group itself. No two backends in a backend service are allowed to use same Instance Group resource. For Network Endpoint Groups this defines list of endpoints. All endpoints of Network Endpoint Group must be hosted on instances located in the same zone as the Network Endpoint Group. Backend services cannot mix Instance Group and Network Endpoint Group backends. When the `load_balancing_scheme` is INTERNAL, only instance groups are supported. Note that you must specify an Instance Group or Network Endpoint Group resource using the fully-qualified URL, rather than a partial URL.

* `description`: An optional description of this resource.
* `max_connections`: The max number of simultaneous connections for the group. Can be used with either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or one of maxConnectionsPerInstance or maxConnectionsPerEndpoint, as appropriate for group type, must be set.

* `fingerprint`: Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.
* `max_connections_per_instance`: The max number of simultaneous connections that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerInstance must be set.

* `protocol`: The protocol this BackendService uses to communicate with backends. The possible values are TCP and UDP, and the default is TCP.
* `max_connections_per_endpoint`: The max number of simultaneous connections that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either CONNECTION or UTILIZATION balancing modes. For CONNECTION mode, either maxConnections or maxConnectionsPerEndpoint must be set.

* `session_affinity`: Type of session affinity to use. The default is NONE. Can be NONE, CLIENT_IP, CLIENT_IP_PROTO, or CLIENT_IP_PORT_PROTO. When the protocol is UDP, this field is not used.
* `max_rate`: The max requests per second (RPS) of the group. Can be used with either RATE or UTILIZATION balancing modes, but required if RATE mode. Either maxRate or one of maxRatePerInstance or maxRatePerEndpoint, as appropriate for group type, must be set.

* `region`: The region where the regional backend service resides.
* `max_rate_per_instance`: The max requests per second (RPS) that a single backend instance can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerInstance must be set.

* `timeout_sec`: How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].
* `max_rate_per_endpoint`: The max requests per second (RPS) that a single backend network endpoint can handle. This is used to calculate the capacity of the group. Can be used in either balancing mode. For RATE mode, either maxRate or maxRatePerEndpoint must be set.

* `max_utilization`: Used when balancingMode is UTILIZATION. This ratio defines the CPU utilization target for the group. Valid range is [0.0, 1.0].

* `connection_draining`: Settings for connection draining

* `draining_timeout_sec`: Time for which instance will be drained (not accept new connections, but still work to finish started).

* `load_balancing_scheme`: This signifies what the ForwardingRule will be used for and can only be INTERNAL for RegionBackendServices
* `creation_timestamp`: Creation timestamp in RFC3339 text format.

* `description`: An optional description of this resource.

* `fingerprint`: Fingerprint of this resource. A hash of the contents stored in this object. This field is used in optimistic locking.

* `health_checks`: The set of URLs to HealthCheck resources for health checking this RegionBackendService. Currently at most one health check can be specified, and a health check is required.

* `id`: The unique identifier for the resource.

* `load_balancing_scheme`: Indicates what kind of load balancing this regional backend service will be used for. A backend service created for one type of load balancing cannot be used with the other(s). Must be `INTERNAL` or `INTERNAL_MANAGED`. Defaults to `INTERNAL`.

* `name`: Name of the resource. Provided by the client when the resource is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression `[a-z]([-a-z0-9]*[a-z0-9])?` which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.

* `protocol`: The protocol this RegionBackendService uses to communicate with backends. Possible values are HTTP, HTTPS, HTTP2, SSL, TCP, and UDP. 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.

* `session_affinity`: Type of session affinity to use. The default is NONE. Session affinity is not applicable if the protocol is UDP.

* `timeout_sec`: How many seconds to wait for the backend before considering it a failed request. Default is 30 seconds. Valid range is [1, 86400].

* `region`: A reference to the region where the regional backend service resides.


## GCP Permissions
Expand Down
12 changes: 7 additions & 5 deletions docs/resources/google_compute_region_backend_services.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,17 +20,19 @@ end
Properties that can be accessed from the `google_compute_region_backend_services` resource:

See [google_compute_region_backend_service.md](google_compute_region_backend_service.md) for more detailed information
* `names`: an array of `google_compute_region_backend_service` name
* `health_checks`: an array of `google_compute_region_backend_service` health_checks
* `backends`: an array of `google_compute_region_backend_service` backends
* `connection_drainings`: an array of `google_compute_region_backend_service` connection_draining
* `creation_timestamps`: an array of `google_compute_region_backend_service` creation_timestamp
* `descriptions`: an array of `google_compute_region_backend_service` description
* `fingerprints`: an array of `google_compute_region_backend_service` fingerprint
* `health_checks`: an array of `google_compute_region_backend_service` health_checks
* `ids`: an array of `google_compute_region_backend_service` id
* `load_balancing_schemes`: an array of `google_compute_region_backend_service` load_balancing_scheme
* `names`: an array of `google_compute_region_backend_service` name
* `protocols`: an array of `google_compute_region_backend_service` protocol
* `session_affinities`: an array of `google_compute_region_backend_service` session_affinity
* `regions`: an array of `google_compute_region_backend_service` region
* `timeout_secs`: an array of `google_compute_region_backend_service` timeout_sec
* `connection_drainings`: an array of `google_compute_region_backend_service` connection_draining
* `load_balancing_schemes`: an array of `google_compute_region_backend_service` load_balancing_scheme
* `regions`: an array of `google_compute_region_backend_service` region

## Filter Criteria
This resource supports all of the above properties as filter criteria, which can be used
Expand Down
Loading