Organizations
CreateOrganization
DeleteOrganization
JoinOrganization
LeaveOrganization
ListMembers
GetOrganization
SetRole
UpdateOrganization
ModelsExpand Collapse
type Organization struct{…}
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are “smeared” so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Examples
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);
Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);
Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();
Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();
Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()
JSON Mapping
In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is “{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z” where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The “Z” suffix indicates the timezone (“UTC”); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by “Z”) when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, “2017-01-15T01:30:15.01Z” encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec ‘%Y-%m-%dT%H:%M:%S.%fZ’. Likewise, in Java, one can use
the Joda Time’s ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.
Tier OrganizationTierThe tier of the organization - free, enterprise or core
The tier of the organization - free, enterprise or core
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are “smeared” so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Examples
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);
Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);
Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();
Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();
Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()
JSON Mapping
In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is “{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z” where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The “Z” suffix indicates the timezone (“UTC”); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by “Z”) when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, “2017-01-15T01:30:15.01Z” encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec ‘%Y-%m-%dT%H:%M:%S.%fZ’. Likewise, in Java, one can use
the Joda Time’s ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.
type OrganizationMember struct{…}
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are “smeared” so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Examples
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);
Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);
Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();
Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();
Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()
JSON Mapping
In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is “{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z” where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The “Z” suffix indicates the timezone (“UTC”); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by “Z”) when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, “2017-01-15T01:30:15.01Z” encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec ‘%Y-%m-%dT%H:%M:%S.%fZ’. Likewise, in Java, one can use
the Joda Time’s ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.
Role OrganizationRole
Status UserStatus
OrganizationsAnnouncement Banner
GetAnnouncementBanner
UpdateAnnouncementBanner
ModelsExpand Collapse
OrganizationsCustom Domains
CreateCustomDomain
DeleteCustomDomain
GetCustomDomain
UpdateCustomDomain
ModelsExpand Collapse
type CustomDomain struct{…}CustomDomain represents a custom domain configuration for an organization
CustomDomain represents a custom domain configuration for an organization
organization_id is the ID of the organization this custom domain belongs to
aws_account_id is the AWS account ID (deprecated: use cloud_account_id)
cloud_account_id is the unified cloud account identifier (AWS Account ID or GCP Project ID)
OrganizationsDomain Verifications
CreateDomainVerification
DeleteDomainVerification
ListDomainVerifications
GetDomainVerification
VerifyDomain
ModelsExpand Collapse
type DomainVerification struct{…}
State DomainVerificationState
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are “smeared” so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Examples
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);
Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);
Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();
Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();
Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()
JSON Mapping
In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is “{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z” where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The “Z” suffix indicates the timezone (“UTC”); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by “Z”) when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, “2017-01-15T01:30:15.01Z” encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec ‘%Y-%m-%dT%H:%M:%S.%fZ’. Likewise, in Java, one can use
the Joda Time’s ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are “smeared” so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Examples
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);
Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);
Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));
Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();
Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();
Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()
JSON Mapping
In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is “{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z” where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The “Z” suffix indicates the timezone (“UTC”); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by “Z”) when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, “2017-01-15T01:30:15.01Z” encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec ‘%Y-%m-%dT%H:%M:%S.%fZ’. Likewise, in Java, one can use
the Joda Time’s ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.
type DomainVerificationState string
OrganizationsInvites
CreateOrganizationInvite
GetOrganizationInviteSummary
GetOrganizationInvite
OrganizationsPolicies
GetOrganizationPolicies
UpdateOrganizationPolicies
ModelsExpand Collapse
type AgentPolicy struct{…}AgentPolicy contains agent-specific policy settings for an organization
AgentPolicy contains agent-specific policy settings for an organization
command_deny_list contains a list of commands that agents are not allowed to execute
scm_tools_disabled controls whether SCM (Source Control Management) tools are disabled for agents
conversation_sharing_policy controls whether agent conversations can be shared
conversation_sharing_policy controls whether agent conversations can be shared
type ConversationSharingPolicy stringConversationSharingPolicy controls how agent conversations can be shared.
ConversationSharingPolicy controls how agent conversations can be shared.
type CrowdStrikeConfig struct{…}CrowdStrikeConfig configures CrowdStrike Falcon sensor deployment
CrowdStrikeConfig configures CrowdStrike Falcon sensor deployment
type CustomSecurityAgent struct{…}CustomSecurityAgent defines a custom security agent configured by an organization admin.
CustomSecurityAgent defines a custom security agent configured by an organization admin.
type OrganizationPolicies struct{…}
AgentPolicy AgentPolicyagent_policy contains agent-specific policy settings
agent_policy contains agent-specific policy settings
command_deny_list contains a list of commands that agents are not allowed to execute
scm_tools_disabled controls whether SCM (Source Control Management) tools are disabled for agents
conversation_sharing_policy controls whether agent conversations can be shared
conversation_sharing_policy controls whether agent conversations can be shared
allowed_editor_ids is the list of editor IDs that are allowed to be used in the organization
allow_local_runners controls whether local runners are allowed to be used in the organization
default_editor_id is the default editor ID to be used when a user doesn’t specify one
default_environment_image is the default container image when none is defined in repo
disable_from_scratch controls whether non-admin users can create blank environments without a Git or URL initializer.
maximum_environments_per_user limits total environments (running or stopped) per user
maximum_running_environments_per_user limits simultaneously running environments per user
members_require_projects controls whether environments can only be created from projects by non-admin users
port_sharing_disabled controls whether user-initiated port sharing is disabled in the organization. System ports (VS Code Browser, agents) are always exempt from this policy.
require_custom_domain_access controls whether users must access via custom domain when one is configured. When true, access via app.gitpod.io is blocked.
restrict_account_creation_to_scim controls whether account creation is restricted to SCIM-provisioned users only. When true and SCIM is configured for the organization, only users provisioned via SCIM can create accounts.
web_browser_disabled controls whether users can open the built-in web browser from environment pages. This does not affect VS Code Browser.
delete_archived_environments_after controls how long archived environments are kept before automatic deletion. 0 means no automatic deletion. Maximum duration is 4 weeks (2419200 seconds).
EditorVersionRestrictions map[string, OrganizationPoliciesEditorVersionRestriction]Optionaleditor_version_restrictions restricts which editor versions can be used.
Maps editor ID to version policy, editor_version_restrictions not set means no restrictions.
If empty or not set for an editor, we will use the latest version of the editor
editor_version_restrictions restricts which editor versions can be used. Maps editor ID to version policy, editor_version_restrictions not set means no restrictions. If empty or not set for an editor, we will use the latest version of the editor
maximum_environment_lifetime controls for how long environments are allowed to be reused. 0 means no maximum lifetime. Maximum duration is 180 days (15552000 seconds).
maximum_environment_timeout controls the maximum timeout allowed for environments in seconds. 0 means no limit (never). Minimum duration is 30 minutes (1800 seconds). value must be 0s (no limit) or at least 1800s (30 minutes):
this == duration('0s') || this >= duration('1800s')project_creation_defaults contains default settings applied to newly created projects.
project_creation_defaults contains default settings applied to newly created projects.
environment_classes specifies default environment classes and their
per-class settings (order, prebuild, warm pool) for newly created projects.
Each entry must reference an existing, enabled, non-local-runner
environment class in the organization.
environment_classes specifies default environment classes and their per-class settings (order, prebuild, warm pool) for newly created projects. Each entry must reference an existing, enabled, non-local-runner environment class in the organization.
prebuild controls whether prebuilds are enabled for this environment class on newly created projects.
insights_enabled controls whether Insights (co-author attribution) is automatically enabled on newly created projects.
prebuilds configures default prebuild settings for newly created projects.
When set, prebuilds can be enabled per environment class via the
environment_classes entries. When absent, prebuilds are not enabled by default.
prebuilds configures default prebuild settings for newly created projects. When set, prebuilds can be enabled per environment class via the environment_classes entries. When absent, prebuilds are not enabled by default.
enable_jetbrains_warmup controls whether JetBrains IDE warmup runs during prebuilds on newly created projects.
prebuild_executor is the service account used to run prebuilds on newly
created projects. Must be a service account (not a user).
prebuild_executor is the service account used to run prebuilds on newly created projects. Must be a service account (not a user).
timeout is the maximum duration allowed for a prebuild to complete. If not specified, defaults to 1 hour. Must be between 5 minutes and 2 hours.
Trigger ProjectCreationDefaultsPrebuildsTriggerOptionaltrigger defines when prebuilds should be created on newly created projects.
trigger defines when prebuilds should be created on newly created projects.
security_agent_policy contains security agent configuration for the organization.
When configured, security agents are automatically deployed to all environments.
security_agent_policy contains security agent configuration for the organization. When configured, security agents are automatically deployed to all environments.
crowdstrike contains CrowdStrike Falcon configuration
crowdstrike contains CrowdStrike Falcon configuration
type ProjectCreationDefaultEnvironmentClass struct{…}ProjectCreationDefaultEnvironmentClass configures a single environment class
in the project creation defaults.
ProjectCreationDefaultEnvironmentClass configures a single environment class in the project creation defaults.
prebuild controls whether prebuilds are enabled for this environment class on newly created projects.
type ProjectCreationDefaultEnvironmentClassWarmPool struct{…}ProjectCreationDefaultEnvironmentClassWarmPool configures warm pool defaults
for an environment class in the project creation defaults.
ProjectCreationDefaultEnvironmentClassWarmPool configures warm pool defaults for an environment class in the project creation defaults.
type ProjectCreationDefaults struct{…}ProjectCreationDefaults contains default settings applied to newly created projects.
ProjectCreationDefaults contains default settings applied to newly created projects.
environment_classes specifies default environment classes and their
per-class settings (order, prebuild, warm pool) for newly created projects.
Each entry must reference an existing, enabled, non-local-runner
environment class in the organization.
environment_classes specifies default environment classes and their per-class settings (order, prebuild, warm pool) for newly created projects. Each entry must reference an existing, enabled, non-local-runner environment class in the organization.
prebuild controls whether prebuilds are enabled for this environment class on newly created projects.
insights_enabled controls whether Insights (co-author attribution) is automatically enabled on newly created projects.
prebuilds configures default prebuild settings for newly created projects.
When set, prebuilds can be enabled per environment class via the
environment_classes entries. When absent, prebuilds are not enabled by default.
prebuilds configures default prebuild settings for newly created projects. When set, prebuilds can be enabled per environment class via the environment_classes entries. When absent, prebuilds are not enabled by default.
enable_jetbrains_warmup controls whether JetBrains IDE warmup runs during prebuilds on newly created projects.
prebuild_executor is the service account used to run prebuilds on newly
created projects. Must be a service account (not a user).
prebuild_executor is the service account used to run prebuilds on newly created projects. Must be a service account (not a user).
timeout is the maximum duration allowed for a prebuild to complete. If not specified, defaults to 1 hour. Must be between 5 minutes and 2 hours.
Trigger ProjectCreationDefaultsPrebuildsTriggerOptionaltrigger defines when prebuilds should be created on newly created projects.
trigger defines when prebuilds should be created on newly created projects.
type ProjectCreationDefaultsPrebuilds struct{…}ProjectCreationDefaultsPrebuilds configures default prebuild settings.
Presence of this message means prebuilds can be enabled for the default environment classes.
ProjectCreationDefaultsPrebuilds configures default prebuild settings. Presence of this message means prebuilds can be enabled for the default environment classes.
enable_jetbrains_warmup controls whether JetBrains IDE warmup runs during prebuilds on newly created projects.
prebuild_executor is the service account used to run prebuilds on newly
created projects. Must be a service account (not a user).
prebuild_executor is the service account used to run prebuilds on newly created projects. Must be a service account (not a user).
timeout is the maximum duration allowed for a prebuild to complete. If not specified, defaults to 1 hour. Must be between 5 minutes and 2 hours.
Trigger ProjectCreationDefaultsPrebuildsTriggerOptionaltrigger defines when prebuilds should be created on newly created projects.
trigger defines when prebuilds should be created on newly created projects.
type SecurityAgentPolicy struct{…}SecurityAgentPolicy contains security agent configuration for an organization.
When enabled, security agents are automatically deployed to all environments.
SecurityAgentPolicy contains security agent configuration for an organization. When enabled, security agents are automatically deployed to all environments.
crowdstrike contains CrowdStrike Falcon configuration
crowdstrike contains CrowdStrike Falcon configuration
OrganizationsScim Configurations
CreateSCIMConfiguration
DeleteSCIMConfiguration
ListSCIMConfigurations
RegenerateSCIMToken
GetSCIMConfiguration
UpdateSCIMConfiguration
ModelsExpand Collapse
type ScimConfiguration struct{…}SCIMConfiguration represents a SCIM 2.0 provisioning configuration
SCIMConfiguration represents a SCIM 2.0 provisioning configuration
organization_id is the ID of the organization this SCIM configuration belongs to
OrganizationsSSO Configurations
CreateSSOConfiguration
DeleteSSOConfiguration
ListSSOConfigurations
GetSSOConfiguration
UpdateSSOConfiguration
ModelsExpand Collapse
type SSOConfiguration struct{…}
ProviderType ProviderTypeprovider_type defines the type of the SSO configuration
provider_type defines the type of the SSO configuration
State SSOConfigurationStatestate is the state of the SSO configuration
state is the state of the SSO configuration
additional_scopes are extra OIDC scopes requested from the identity provider during sign-in.
claims are key/value pairs that defines a mapping of claims issued by the IdP.
claims_expression is a CEL (Common Expression Language) expression evaluated against
the OIDC token claims during login. When set, the expression must evaluate to true
for the login to succeed. The expression has access to a claims variable containing
all token claims as a map. Example: claims.email_verified && claims.email.endsWith("@example.com")