Implement SAST Configuration form submission
What does this MR do?
Implement SAST Configuration form submission
Part of the SAST Configuration UI feature, this implements form submission behaviour, via a regular POST request. A future iteration will replace this with a GraphQL mutation.
Specifically, this adds a new ConfigurationForm
component that's responsible for collecting the form vales and submitting them to the backend, and redirecting the user to the newly created merge request.
Addresses #223879 (closed).
Screenshots
Note that the backend work (#229976 (closed), #220575 (closed)) for this isn't complete yet, which means:
- The fields visible in the form do not match those in the designs (i.e., the particular fields, missing descriptions, input size, initial value).
- The created MR doesn't have quite the right structure/contents.
None of that should block this MR, though!
Success flow | Error flow |
---|---|
success_flow | error_flow |
Draft
This MR is in Draft, as it's blocked by !38318 (merged).
Feature flag
This feature is behind the sast_configuration_ui
feature flag, which will be removed or enabled by default in #231357 (closed).
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