lukayeh opened a new issue, #7611: URL: https://github.com/apache/incubator-devlake/issues/7611
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues. ### What happened i’d like to disable the gitlab-collectDeployment but having difficulties doing so via environments variables: ``` "plugin": "gitlab", "subtasks": [ "CollectDeployment", ``` this is what I’m using: `ENABLE_SUBTASKS_BY_DEFAULT="gitlab:CollectDeployment:false"` ### What do you expect to happen CollectDeployments phase is removed from transform. ### How to reproduce set: `ENABLE_SUBTASKS_BY_DEFAULT="gitlab:CollectDeployment:false` ### Anything else we had a look at the source (even v1.0.0-beta6) the Gilab plugin blueprint creation bypasses this function: https://github.com/apache/incubator-devlake/blob/v1.0.0-beta6/backend/helpers/pluginhelper/api/pipeline_plan.go#L60 The above function utilises the ENABLE_SUBTASKS_BY_DEFAULT to enable or disable subtasks for the plugin. No other part of the code utilises that environment variable. The Gitlab plugin bypasses MakePipelinePlanTask in the helper by calling MakePipelinePlanSubtasks helper instead which is what is ultimately called by MakePipelinePlanTask: https://github.com/apache/incubator-devlake/blob/v1.0.0-beta6/backend/plugins/gitlab/api/blueprint_v200.go#L127 ### Version v0.21.0@ac4f7fe ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@devlake.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
