You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/AccountMembersApi.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ nil (empty response body)
88
88
89
89
Get account member
90
90
91
-
Get a single account member by ID. `me` is a reserved value for the `id` parameter and returns the caller's member information.
91
+
Get a single account member by member ID. `me` is a reserved value for the `id` parameter and returns the caller's member information.
92
92
93
93
### Examples
94
94
@@ -159,7 +159,7 @@ end
159
159
160
160
List account members
161
161
162
-
Return a list of account members. By default, this returns the first 20 members. Page through this list with the `limit` parameter and by following the `first`, `prev`, `next`, and `last` links in the returned `_links` field. These links are not present if the pages they refer to don't exist. For example, the `first` and `prev` links will be missing from the response on the first page. ### Filtering members LaunchDarkly supports three fields for filters: `query`, `role`, and `lastSeen`: - `query` is a string that matches against the members' emails and names. It is not case sensitive. - `role` is a `|` separated list of roles and custom roles. It filters the list to members who have any of the roles in the list. For the purposes of this filtering, `Owner` counts as `Admin`. - `lastSeen` is a JSON object in one of the following formats: - `{\"never\": true}` - Members that have never been active, such as those who have not accepted their invitation to LaunchDarkly, or have not logged in after being provisioned via SCIM. - `{\"noData\": true}` - Members that have not been active since LaunchDarkly began recording last seen timestamps. - `{\"before\": 1608672063611}` - Members that have not been active since the provided value, which should be a timestamp in Unix epoch milliseconds. For example, the filter `query:abc,role:admin|customrole` matches members with the string `abc` in their email or name, ignoring case, who also are either an an `Owner` or `Admin` or have the custom role `customrole`. ### Sorting members LaunchDarkly supports two fields for sorting: `displayName` and `lastSeen`: - `displayName` sorts by first + last name, using the member's email if no name is set. - `lastSeen` sorts by the `_lastSeen` property. LaunchDarkly considers members that have never been seen or have no data the oldest.
162
+
Return a list of account members. By default, this returns the first 20 members. Page through this list with the `limit` parameter and by following the `first`, `prev`, `next`, and `last` links in the returned `_links` field. These links are not present if the pages they refer to don't exist. For example, the `first` and `prev` links will be missing from the response on the first page. ### Filtering members LaunchDarkly supports three fields for filters: `query`, `role`, and `lastSeen`: - `query` is a string that matches against the members' emails and names. It is not case sensitive. - `role` is a `|` separated list of roles and custom roles. It filters the list to members who have any of the roles in the list. For the purposes of this filtering, `Owner` counts as `Admin`. - `team` is a string that matches against the key of the teams the members belong to. It is not case sensitive. - `lastSeen` is a JSON object in one of the following formats: - `{\"never\": true}` - Members that have never been active, such as those who have not accepted their invitation to LaunchDarkly, or have not logged in after being provisioned via SCIM. - `{\"noData\": true}` - Members that have not been active since LaunchDarkly began recording last seen timestamps. - `{\"before\": 1608672063611}` - Members that have not been active since the provided value, which should be a timestamp in Unix epoch milliseconds. For example, the filter `query:abc,role:admin|customrole` matches members with the string `abc` in their email or name, ignoring case, who also are either an an `Owner` or `Admin` or have the custom role `customrole`. ### Sorting members LaunchDarkly supports two fields for sorting: `displayName` and `lastSeen`: - `displayName` sorts by first + last name, using the member's email if no name is set. - `lastSeen` sorts by the `_lastSeen` property. LaunchDarkly considers members that have never been seen or have no data the oldest.
limit:789, # Integer | The number of members to return in the response. Defaults to 20.
180
-
offset:789, # Integer | Where to start in the list. This is for use with pagination. For example, an offset of 10 would skip the first ten items and then return the next `limit` items.
180
+
offset:789, # Integer | Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query `limit`.
181
181
filter:'filter_example', # String | A comma-separated list of filters. Each filter is of the form `field:value`. Supported fields are explained above.
182
182
sort:'sort_example'# String | A comma-separated list of fields to sort by. Fields prefixed by a dash ( - ) sort in descending order.
183
183
}
@@ -214,7 +214,7 @@ end
214
214
| Name | Type | Description | Notes |
215
215
| ---- | ---- | ----------- | ----- |
216
216
|**limit**|**Integer**| The number of members to return in the response. Defaults to 20. |[optional]|
217
-
|**offset**|**Integer**| Where to start in the list. This is for use with pagination. For example, an offset of 10 would skip the first ten items and then return the next `limit` items. |[optional]|
217
+
|**offset**|**Integer**| Where to start in the list. This is for use with pagination. For example, an offset of 10 skips the first ten items and then returns the next items in the list, up to the query `limit`. |[optional]|
218
218
|**filter**|**String**| A comma-separated list of filters. Each filter is of the form `field:value`. Supported fields are explained above. |[optional]|
219
219
|**sort**|**String**| A comma-separated list of fields to sort by. Fields prefixed by a dash ( - ) sort in descending order. |[optional]|
> ### Full use of this API resource is only available to accounts with paid subscriptions > > The ability to bulk invite members is a paid feature. Single members may be invited if not on a paid plan. Invite one or more new members to join an account. Each member is sent an invitation. Members with \"admin\" or \"owner\" roles may create new members, as well as anyone with a \"createMember\" permission for \"member/\\*\". If a member cannot be invited, the entire request is rejected and no members are invited from that request. Each member _must_ have an `email` field and either a `role` or a `customRoles` field. If any of the fields are not populated correctly, the request is rejected with the reason specified in the \"message\" field of the response. Requests to create account members will not work if SCIM is enabled for the account. _No more than 50 members may be created per request._ A request may also fail because of conflicts with existing members. These conflicts are reported using the additional `code` and `invalid_emails` response fields with the following possible values for `code`: - **email_already_exists_in_account**: A member with this email address already exists in this account. - **email_taken_in_different_account**: A member with this email address exists in another account. - **duplicate_email**s: This request contains two or more members with the same email address. A request that fails for one of the above reasons returns an HTTP response code of 400 (Bad Request).
387
+
> ### Full use of this API resource is only available to customers on an Enterprise plan > > The ability to bulk invite members is an Enterprise feature. On a starter or Pro plan? You can invite members individually. Invite one or more new members to join an account. Each member is sent an invitation. Members with \"admin\" or \"owner\" roles may create new members, as well as anyone with a \"createMember\" permission for \"member/\\*\". If a member cannot be invited, the entire request is rejected and no members are invited from that request. Each member _must_ have an `email` field and either a `role` or a `customRoles` field. If any of the fields are not populated correctly, the request is rejected with the reason specified in the \"message\" field of the response. Requests to create account members will not work if SCIM is enabled for the account. _No more than 50 members may be created per request._ A request may also fail because of conflicts with existing members. These conflicts are reported using the additional `code` and `invalid_emails` response fields with the following possible values for `code`: - **email_already_exists_in_account**: A member with this email address already exists in this account. - **email_taken_in_different_account**: A member with this email address exists in another account. - **duplicate_email**s: This request contains two or more members with the same email address. A request that fails for one of the above reasons returns an HTTP response code of 400 (Bad Request).
388
388
389
389
### Examples
390
390
@@ -400,7 +400,7 @@ LaunchDarklyApi.configure do |config|
Copy file name to clipboardExpand all lines: docs/ActionInputRep.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -4,15 +4,15 @@
4
4
5
5
| Name | Type | Description | Notes |
6
6
| ---- | ---- | ----------- | ----- |
7
-
|**instructions**|**Object**||[optional]|
7
+
|**instructions**|**Object**|An array of instructions for the stage. Each object in the array uses the semantic patch format for updating a feature flag.|[optional]|
environment_key ='environment_key_example'# String | The environment key for the target environment
504
+
create_copy_flag_config_approval_request_request =LaunchDarklyApi::CreateCopyFlagConfigApprovalRequestRequest.new({description:'copy flag settings to another environment', source:LaunchDarklyApi::SourceFlag.new({key:'example-environment-key'})}) # CreateCopyFlagConfigApprovalRequestRequest |
505
505
506
506
begin
507
507
# Create approval request to copy flag configurations across environments
@@ -536,7 +536,7 @@ end
536
536
| ---- | ---- | ----------- | ----- |
537
537
|**project_key**|**String**| The project key ||
538
538
|**feature_flag_key**|**String**| The feature flag key ||
539
-
|**environment_key**|**String**| The environment key ||
539
+
|**environment_key**|**String**| The environment key for the target environment ||
Copy file name to clipboardExpand all lines: docs/AuditLogApi.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ end
95
95
96
96
Get audit log entry
97
97
98
-
Fetch a detailed audit log entry representation. The detailed representation includes several fields that are not present in the summary representation: - `delta`: the JSON patch body that was used in the request to update the entity - `previousVersion`: a JSON representation of the previous version of the entity - `currentVersion`: a JSON representation of the current version of the entity
98
+
Fetch a detailed audit log entry representation. The detailed representation includes several fields that are not present in the summary representation, including: - `delta`: the JSON patch body that was used in the request to update the entity - `previousVersion`: a JSON representation of the previous version of the entity - `currentVersion`: a JSON representation of the current version of the entity
0 commit comments