Support ci_forward_deployment_enabled in edit project API
What does this MR do?
Related to #212621 (closed)
Ok. So a couple things:
- This parameter is being changed to
ci_forward_deployment_enabled
throughout the codebase to indicate that this is a property ofproject.ci_cd_settings
rather than a property that's directly onproject
itself. - Because
ci_cd_settings
is created in anafter_create
hook, you can not provide this parameter in the API at project creation time. As such this parameter will not work withPOST /api/v4/projects
. - After creation of the project however, you can update this parameter via the API
PUT /api/v4/projects/:id
. - This is an iteration. A subsequent step in the iteration process for this might be to somehow make it so
ci_forward_deployment_enabled
can be allowed in the creation API as well. But for now that is outside the scope of this MR.
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
Edited by Amy Troschinetz