Resources in custom roles
Read time: 1 minute
Last edited: Feb 12, 2020
This topic explains how custom roles use resources.
Almost everything in LaunchDarkly is a resource, including:
- Feature flags
- Custom roles
When you change a feature flag's rollout rules, or rename an environment, you are accessing a particular resource.
LaunchDarkly uses a resource specifier syntax to name resources or collections of resources. This is a precise but flexible categorizing taxonomy that allows you to name any resource in a way that accurately reflects the information structures your organization uses.
The pattern looks like this:
The example above shows two tags separated by a comma. Tags are also optional. If you don't need to use any tags, you can omit the semicolon (
;) and all content following.
In the example below, we create a resource that names all of the projects in an account:
The resource syntax accepts globs, so you can name collections of resources with
*. You can also name a specific
project by ID.
In the example below, we name a project by the
You can name sets of resources all the way down to the tag level.
In the example below, we name all projects with the
The term scoping refers to granting or restricting permissions and access to a resource based on relationships the resource has. Resources can be scoped within parent resources.
For example, metrics are scoped within a project, and feature flags are scoped within a project and environment.
Name scoped resources by using the resource syntax structure depicted below.
In the following example, we name all feature flags across all environments:
In the example above,
proj/*:indicates that all named projects will be included in the list of results.
env/*: indicates that all environments will be included in the list of results.
flag/*: indicates that all flags will be included in the list of results.
Because of the range of resources referenced in this example, we can say it has very broad scope.
For a more refined example, we could name all feature flags whose keys start with
|Resource Type||Resource Scope|
|Top-level resource. Projects have no parent resource. Write it as |
|A child resources of |