Add integration with BE based on mocks
What does this MR do?
http_integrations_list && multiple_http_integrations_custom_mapping
Ads BE-like interaction to the Mapping Builder form based on mocks. Wherever a call to backend should be done we currently Promise.resolve(mockData) and then work with the result. The data format is defined now. backend part is under development. This is a 3rd MR in a row
To check navigate to Settings=>Operations=>Alerts=> Select HTTP Endpoint (in Select integration type dropdown)
Plan for the feature rollout on frontend side
| header | header |
|---|---|
| Introduce feature flag, add placeholder for Mapping Builder |
|
| Add mapping builder form with mocked data |
|
| Add linking arrow |
|
| Mock communication with BE for sample payload parse and read | workflowin review - current MR |
| Integrate parsing alert payload with backend | |
| Send test alert - integration with backend | |
| Save form - integration with backend | |
| Remove feature flag |
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
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
Related to #262707 (closed)
Edited by Olena Horal-Koretska