Skip to content

Commit b73ad38

Browse files
api-clients-generation-pipeline[bot]ci.datadog-api-spec
andauthored
Enable Rust sdk generation pipeline (#1910)
Co-authored-by: ci.datadog-api-spec <[email protected]>
1 parent 8ca772a commit b73ad38

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

.apigentools-info

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
"spec_versions": {
55
"v1": {
66
"apigentools_version": "1.6.6",
7-
"regenerated": "2024-03-21 18:00:28.881112",
8-
"spec_repo_commit": "65baee0e"
7+
"regenerated": "2024-03-21 19:44:29.077421",
8+
"spec_repo_commit": "7b0d4cbe"
99
},
1010
"v2": {
1111
"apigentools_version": "1.6.6",
12-
"regenerated": "2024-03-21 18:00:28.897695",
13-
"spec_repo_commit": "65baee0e"
12+
"regenerated": "2024-03-21 19:44:29.098141",
13+
"spec_repo_commit": "7b0d4cbe"
1414
}
1515
}
1616
}

tests/v2/features/logs_custom_destinations.feature

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Feature: Logs Custom Destinations
7575
And the response "data.attributes.forward_tags_restriction_list" array contains value "host"
7676
And the response "data.attributes.forward_tags_restriction_list_type" is equal to "ALLOW_LIST"
7777

78-
@skip-java @skip-python @skip-typescript @team:DataDog/logs-backend
78+
@skip-java @skip-python @skip-rust @skip-typescript @team:DataDog/logs-backend
7979
Scenario: Create a custom destination returns "Bad Request" response
8080
Given new "CreateLogsCustomDestination" request
8181
And body with value {"data": {"attributes": {"name": "Nginx logs"}, "type": "custom_destination"}}

tests/v2/features/organizations.feature

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Feature: Organizations
99
And an instance of "Organizations" API
1010
And new "UploadIdPMetadata" request
1111

12-
@skip-go @skip-java @skip-python @skip-ruby @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/team-aaa-identity
12+
@skip-go @skip-java @skip-python @skip-ruby @skip-rust @skip-terraform-config @skip-typescript @skip-validation @team:DataDog/team-aaa-identity
1313
Scenario: Upload IdP metadata returns "Bad Request - caused by either malformed XML or invalid SAML IdP metadata" response
1414
Given request contains "idp_file" parameter with value "fixtures/organizations/saml_configurations/invalid_idp_metadata.xml"
1515
When the request is sent

0 commit comments

Comments
 (0)