You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API for creating Devtron App Workflow : /orchestrator/core/v1beta1/application/workflow, will create invalid CI Material incase of linked CI if the payload contains invalid GitMaterialId. As it creates the workflow successfully with corrupted data, we will not be able to update branch name in linked CI pipeline.
Hit the Create Devtron App Workflow API: /orchestrator/core/v1beta1/application/workflow with linked CI Payload. Use an invalid combination of GitMaterialId and ParentAppId. (GitMaterialId should exist in the DB but not attached to the specified ParentAppId)
It will successfully create the workflow.
Now try to update branch (That does exist for ParentApp GitMaterial, but not in the GitMaterialId that have been provided in the payload) for the CI pipeline. It would break as the GitMaterial is different.
👍 Expected behavior
There Should be Validation on GitMaterialId before Creating workflow
👎 Actual Behavior
It saves corrupted data if provided by the User
☸ Kubernetes version
NA
Cloud provider
NA
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
📜 Description
The API for creating Devtron App Workflow :
/orchestrator/core/v1beta1/application/workflow
, will create invalid CI Material incase of linked CI if the payload contains invalid GitMaterialId. As it creates the workflow successfully with corrupted data, we will not be able to update branch name in linked CI pipeline.This exposed the Issue #3797
👟 Reproduction steps
/orchestrator/core/v1beta1/application/workflow
with linked CI Payload. Use an invalid combination of GitMaterialId and ParentAppId. (GitMaterialId should exist in the DB but not attached to the specified ParentAppId)👍 Expected behavior
There Should be Validation on GitMaterialId before Creating workflow
👎 Actual Behavior
It saves corrupted data if provided by the User
☸ Kubernetes version
NA
Cloud provider
🌍 Browser
Chrome
🧱 Your Environment
No response
✅ Proposed Solution
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
AB#5213
The text was updated successfully, but these errors were encountered: