Roles

Envless.roles.update

Change a custom role name, description or permissions

def update(id, patch = nil, timeout: nil, **fields)

Patches a custom role. Every field is optional, but permissions: is a full replacement rather than a merge: send the complete list the role should end up with, or leave the key out entirely to keep the current one. Passing description: nil clears the description.

System roles are immutable. Patching owner, admin or viewer fails with 409 role.immutable however harmless the field, so gate the call on isSystem. The same two ceilings as creation apply to the permission list: the never assignable permissions fail validation with 400 request.body_invalid, and anything the key owner does not hold themselves fails with 403 auth.permission_denied.

A permission change is live immediately for every member holding the role. Existing API keys owned by those members are not re-clamped by this call, only by a change to the member role, so a key can keep a scope its owner no longer has until that key is updated.

Example

ruby
require "envless/sdk"

role = Envless.roles.list_all(search: "deploy").fetch(0)

updated = Envless.roles.update(
  role[:id],
  description: nil,
  permissions: %w[projects:read environments:read variables:read]
)

puts updated[:permissions]

Parameters

ParameterTypeRequiredDescription
idStringYesRole id from roles.list, which must belong to a custom role.
patchrole_patchNoThe fields below as one Hash, with Symbol or String keys, in place of the keywords.
name:StringNoNew display name, still subject to case insensitive uniqueness.
description:String | nilNoNew description, or nil to clear the existing one.
permissions:Array[String]NoComplete replacement permission list, not a set of additions.
timeout:Integer | Float | RationalNoSeconds each attempt of this call may take, redirects and the response body included, before it raises Envless::NetworkError with timeout? set. Overrides the client's timeout for this call, and 0 turns the limit off.

Returns

role_resource reflecting the stored role after the patch.

Worth knowing

  • Sending permissions: [] strips every permission from the role, which is very different from omitting the key.
  • Read the role back with get before patching if you intend to add one permission, since you have to resend the ones you want to keep.
  • A successful patch emits the role.updated webhook event.

Required scopes

roles:write

Underlying endpoint

PATCH /roles/{id}

Request and response schema, every error code, and a live playground.

In TypeScript

envless.roles.update()

The same method in @goenvless/sdk, with the same request, retries and errors.