Skip to content

Reassign aaa-identity CODEOWNERS to delegated-auth-login and org-management #3713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
api-clients-generation-pipeline merged 1 commit into from
Apr 9, 2026
Merged

Reassign aaa-identity CODEOWNERS to delegated-auth-login and org-management #3713

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions src/test/resources/com/datadog/api/client/v1/api/organizations.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,87 +8,87 @@ Feature: Organizations
And a valid "appKeyAuth" key in the system
And an instance of "Organizations" API

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Create a child organization returns "Bad Request" response
Given new "CreateChildOrg" request
And body with value {"billing": {"type": "parent_billing"}, "name": "New child org", "subscription": {"type": "pro"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Create a child organization returns "OK" response
Given new "CreateChildOrg" request
And body with value {"billing": {"type": "parent_billing"}, "name": "New child org", "subscription": {"type": "pro"}}
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Get organization information returns "Bad Request" response
Given new "GetOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Get organization information returns "OK" response
Given new "GetOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: List your managed organizations returns "OK" response
Given new "ListOrgs" request
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Spin-off Child Organization returns "Bad Request" response
Given new "DowngradeOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Spin-off Child Organization returns "OK" response
Given new "DowngradeOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Update your organization returns "Bad Request" response
Given new "UpdateOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
And body with value {"billing": {"type": "parent_billing"}, "description": "some description", "name": "New child org", "public_id": "abcdef12345", "settings": {"private_widget_share": false, "saml": {"enabled": false}, "saml_autocreate_access_role": "ro", "saml_autocreate_users_domains": {"domains": ["example.com"], "enabled": false}, "saml_can_be_enabled": false, "saml_idp_endpoint": "https://my.saml.endpoint", "saml_idp_initiated_login": {"enabled": false}, "saml_idp_metadata_uploaded": false, "saml_login_url": "https://my.saml.login.url", "saml_strict_mode": {"enabled": false}}, "subscription": {"type": "pro"}, "trial": false}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Update your organization returns "OK" response
Given new "UpdateOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
And body with value {"billing": {"type": "parent_billing"}, "description": "some description", "name": "New child org", "public_id": "abcdef12345", "settings": {"private_widget_share": false, "saml": {"enabled": false}, "saml_autocreate_access_role": "ro", "saml_autocreate_users_domains": {"domains": ["example.com"], "enabled": false}, "saml_can_be_enabled": false, "saml_idp_endpoint": "https://my.saml.endpoint", "saml_idp_initiated_login": {"enabled": false}, "saml_idp_metadata_uploaded": false, "saml_login_url": "https://my.saml.login.url", "saml_strict_mode": {"enabled": false}}, "subscription": {"type": "pro"}, "trial": false}
When the request is sent
Then the response status is 200 OK

@skip @team:DataDog/team-aaa-identity
@skip @team:DataDog/org-management
Scenario: Upload IdP metadata returns "Bad Request" response
Given new "UploadIdPForOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
And request contains "idp_file" parameter with value "./idp_metadata_invalid.xml"
When the request is sent
Then the response status is 400 Bad Request

@skip @team:DataDog/team-aaa-identity
@skip @team:DataDog/org-management
Scenario: Upload IdP metadata returns "OK" response
Given new "UploadIdPForOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
And request contains "idp_file" parameter with value "./idp_metadata.xml"
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Upload IdP metadata returns "Unsupported Media Type" response
Given new "UploadIdPForOrg" request
And request contains "public_id" parameter from "REPLACE.ME"
Expand Down
26 changes: 13 additions & 13 deletions src/test/resources/com/datadog/api/client/v1/api/users.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,93 +7,93 @@ Feature: Users
And a valid "appKeyAuth" key in the system
And an instance of "Users" API

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Create a user returns "Bad Request" response
Given new "CreateUser" request
And body with value {"access_role": "ro", "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Create a user returns "Conflict" response
Given new "CreateUser" request
And body with value {"access_role": "ro", "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Create a user returns "User created" response
Given new "CreateUser" request
And body with value {"access_role": "ro", "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 200 User created

@replay-only @team:DataDog/team-aaa-identity
@replay-only @team:DataDog/org-management
Scenario: Create a user returns null access role
Given new "CreateUser" request
And body with value {"access_role": null, "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 200 User created
And the response "user.access_role" is equal to null

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Disable a user returns "Bad Request" response
Given new "DisableUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Disable a user returns "Not Found" response
Given new "DisableUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Disable a user returns "User disabled" response
Given new "DisableUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 User disabled

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Get user details returns "Not Found" response
Given new "GetUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Get user details returns "OK for get user" response
Given new "GetUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 200 OK for get user

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: List all users returns "OK" response
Given new "ListUsers" request
When the request is sent
Then the response status is 200 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Update a user returns "Bad Request" response
Given new "UpdateUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
And body with value {"access_role": "ro", "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Update a user returns "Not Found" response
Given new "UpdateUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
And body with value {"access_role": "ro", "disabled": false, "email": "test@datadoghq.com", "handle": "test@datadoghq.com", "name": "test user"}
When the request is sent
Then the response status is 404 Not Found

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/org-management
Scenario: Update a user returns "User updated" response
Given new "UpdateUser" request
And request contains "user_handle" parameter from "REPLACE.ME"
Expand Down
26 changes: 13 additions & 13 deletions src/test/resources/com/datadog/api/client/v2/api/authn_mappings.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,21 +10,21 @@ Feature: AuthN Mappings
And a valid "appKeyAuth" key in the system
And an instance of "AuthNMappings" API

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Create an AuthN Mapping returns "Bad Request" response
Given new "CreateAuthNMapping" request
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Create an AuthN Mapping returns "Not Found" response
Given new "CreateAuthNMapping" request
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/team-aaa-identity
@team:DataDog/delegated-auth-login
Scenario: Create an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And new "CreateAuthNMapping" request
Expand All @@ -35,14 +35,14 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Delete an AuthN Mapping returns "Not Found" response
Given new "DeleteAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/team-aaa-identity
@team:DataDog/delegated-auth-login
Scenario: Delete an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -51,31 +51,31 @@ Feature: AuthN Mappings
When the request is sent
Then the response status is 204 OK

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Edit an AuthN Mapping returns "Bad Request" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 400 Bad Request

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Edit an AuthN Mapping returns "Conflict" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 409 Conflict

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Edit an AuthN Mapping returns "Not Found" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/team-aaa-identity
@team:DataDog/delegated-auth-login
Scenario: Edit an AuthN Mapping returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -89,22 +89,22 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "Development"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Edit an AuthN Mapping returns "Unprocessable Entity" response
Given new "UpdateAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
And body with value {"data": {"attributes": {"attribute_key": "member-of", "attribute_value": "Development"}, "id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "relationships": {"role": {"data": {"id": "3653d3c6-0c75-11ea-ad28-fb5701eabc7d", "type": "roles"}}}, "type": "authn_mappings"}}
When the request is sent
Then the response status is 422 Unprocessable Entity

@generated @skip @team:DataDog/team-aaa-identity
@generated @skip @team:DataDog/delegated-auth-login
Scenario: Get an AuthN Mapping by UUID returns "Not Found" response
Given new "GetAuthNMapping" request
And request contains "authn_mapping_id" parameter from "REPLACE.ME"
When the request is sent
Then the response status is 404 Not Found

@team:DataDog/team-aaa-identity
@team:DataDog/delegated-auth-login
Scenario: Get an AuthN Mapping by UUID returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand All @@ -117,7 +117,7 @@ Feature: AuthN Mappings
And the response "data.attributes.attribute_value" is equal to "{{ unique }}"
And the response "data.relationships.role.data.id" is equal to "{{ role.data.id }}"

@team:DataDog/team-aaa-identity
@team:DataDog/delegated-auth-login
Scenario: List all AuthN Mappings returns "OK" response
Given there is a valid "role" in the system
And there is a valid "authn_mapping" in the system
Expand Down
Loading
Loading