list_environment_targets
GET
/v1/environment-targets
const url = 'https://app.everruns.com/api/v1/environment-targets';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://app.everruns.com/api/v1/environment-targetsList the environment targets this deployment can offer, with the capabilities each one actually has.
Responses
Section titled “Responses”Available environment targets
Media typeapplication/json
Response body for the list_environment_targets operation.
object
items
required
Array<object>
One target this deployment can offer, and what it can do.
object
available
required
Whether this deployment can actually run it right now.
boolean
capabilities
required
What the environment can actually do.
Read this before assuming a shell behaves like Linux. Bashkit reports
native_processes: false, which is why a build fails there; the answer is
available before the first turn rather than after a confusing tool error.
object
native_processes
required
boolean
network_enforced
required
boolean
packages
required
boolean
portable_checkpoint
required
boolean
ports
required
boolean
pty
required
boolean
containment_levels
required
Containment levels this target supports, weakest first.
Array<string>
durability
required
string
kind
required
string
provider
string | null
reason
Why it is unavailable. Present only when available is false.
string | null
Examplegenerated
{ "items": [ { "available": true, "capabilities": { "native_processes": true, "network_enforced": true, "packages": true, "portable_checkpoint": true, "ports": true, "pty": true }, "containment_levels": [ "example" ], "durability": "example", "kind": "example", "provider": "example", "reason": "example" } ]}