Allow filtering alertManagementIntegrations GraphQL by ID [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
Related to #321674 (closed)
All the discussions related to implementation details can be found here !56647 (closed)
Example queries
`alertManagementIntegrations` with Http Integration ID
Query
query Extract($fullPath: ID!, $id: ID!) {
project(fullPath: $fullPath) {
alertManagementIntegrations(id: $id) {
nodes {
id
active
name
... on AlertManagementHttpIntegration {
payloadExample
payloadAlertFields {
type path label
}
}
}
}
}
}
Query Variables
{
"fullPath": "ck3g/new-playground",
"id": "gid://gitlab/AlertManagement::HttpIntegration/5"
}
`alertManagementIntegrations` with Prometheus Integration ID
Query
query Extract($fullPath: ID!, $id: ID!) {
project(fullPath: $fullPath) {
alertManagementIntegrations(id: $id) {
nodes {
id
active
name
... on AlertManagementHttpIntegration {
payloadExample
payloadAlertFields {
type path label
}
}
}
}
}
}
Query Variables
{
"fullPath": "ck3g/new-playground",
"id": "gid://gitlab/PrometheusService/12"
}
`alertManagementHttIntegrations` with ID
Query
query Extract($fullPath: ID!, $id: ID!) {
project(fullPath: $fullPath) {
alertManagementHttpIntegrations(id: $id) {
nodes {
id
active
name
payloadExample
payloadAlertFields {
type path label
}
}
}
}
}
Query Variables
{
"fullPath": "ck3g/new-playground",
"id": "gid://gitlab/AlertManagement::HttpIntegration/5"
}
Screenshots
alertManagementIntegrations with Http Integration ID |
alertManagementIntegrations with Prometheus Integration ID |
alertManagementHttIntegrations with ID |
---|---|---|
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. - [-] I have not included a changelog entry because _____.
-
- [-] Documentation (if required)
-
Code review guidelines -
Merge request performance guidelines -
Style guides - [-] Database guides
-
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. - [-] Tested in all supported browsers
- [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
- [-] Label as security and @ mention
@gitlab-com/gl-security/appsec
- [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
- [-] Security reports checked/validated by a reviewer from the AppSec team