Updates an environment by name
PUT /api/admin/environments/update/:name
Given an environment by name updates the environment with the given payload. Note that name, enabled and protected cannot be changed by this API
Request
Path Parameters
- name string required
 
- application/json
 
Body
required
updateEnvironmentSchema
- type string
Updates the type of environment (i.e. development or production).
 - sortOrder integer
Changes the sort order of this environment.
 
- 200
 - 400
 - 401
 
environmentSchema
- application/json
 
- Schema
 - Example (from schema)
 
Schema
- name string required
The name of the environment
 - type string required
The type of environment.
 - enabled boolean required
trueif the environment is enabled for the project, otherwisefalse. - protected boolean required
trueif the environment is protected, otherwisefalse. A protected environment can not be deleted. - sortOrder integer required
Priority of the environment in a list of environments, the lower the value, the higher up in the list the environment will appear. Needs to be an integer
 - projectCount integer nullable
The number of projects with this environment
 - apiTokenCount integer nullable
The number of API tokens for the project environment
 - enabledToggleCount integer nullable
The number of enabled toggles for the project environment
 
{
  "name": "my-dev-env",
  "type": "development",
  "enabled": true,
  "protected": true,
  "sortOrder": 3,
  "projectCount": 10,
  "apiTokenCount": 6,
  "enabledToggleCount": 10
}
The request data does not match what we expect.
- application/json
 
- Schema
 - Example (from schema)
 
Schema
- id string
The ID of the error instance
 - name string
The name of the error kind
 - message string
A description of what went wrong.
 
{
  "id": "9c40958a-daac-400e-98fb-3bb438567008",
  "name": "ValidationError",
  "message": "The request payload you provided doesn't conform to the schema. The .parameters property should be object. You sent []."
}
Authorization information is missing or invalid. Provide a valid API token as the authorization header, e.g. authorization:*.*.my-admin-token.
- application/json
 
- Schema
 - Example (from schema)
 
Schema
- id string
The ID of the error instance
 - name string
The name of the error kind
 - message string
A description of what went wrong.
 
{
  "id": "9c40958a-daac-400e-98fb-3bb438567008",
  "name": "AuthenticationRequired",
  "message": "You must log in to use Unleash. Your request had no authorization header, so we could not authorize you. Try logging in at /auth/simple/login."
}