Create a test policy
POST/v1/bubble-policies
Sets up an isolated network a test can run in: the operator project it is built in, the address ranges it allocates from, whether its copies may send traffic out of it, the jump host health checks run from, the health check types allowed, the addresses it must prove it cannot reach, and how long a test under it may last. A registration names the policy its tests run under, and a test can name one itself.
Operator only: needs a system-scoped token.
Request
Responses
- 201
- 400
- 401
- 403
- 409
- 413
- 415
- 422
- default
Created
Bad Request.
invalid_request: The body is not a single JSON object, names a field this operation does not take, or gives a value of the wrong type.
Unauthorized.
unauthenticated: The token is missing, expired or not valid.
Forbidden.
forbidden: The token is not a system-scoped admin token.
Conflict.
conflict: A test policy with this name already exists. Or project_id names no project here, or one that is disabled.
Request Entity Too Large.
body_too_large: The body is larger than the service accepts.
Unsupported Media Type.
unsupported_media_type: The body is not sent as application/json.
Unprocessable Entity.
validation_failed: name, project_id or network_cidrs is missing. A range is not in CIDR form or has host bits set. max_duration is not a duration from 10m to 168h. A permitted check is neither tcp nor http. An isolation canary is not host:port with a port from 1 to 65535, or canaries are given on a strict policy with no jump host. fields names each.
An error, as an RFC 7807 problem document.