Closed gasci closed 3 days ago
good idea
Thank you for the feedback. And is it possible to release a v5 after these additions? We are using this action every day and we depend on this feature to make our CI/CD pipelines more flexible.
Has there been any update on this feature? This feature is really crucial for our pipelines not to push the same image multiple times.
This is resolved as part of adding dbt deploy support in deploy-action, as we introduced a new deploy-type
field, that allows users to configure a dags-only
deploy if the trigger event only had file changes in the dags
folder.
Reference PR that solves the issue: #74
Does it forcefully dag-only deploy even though the file changes say otherwise?
yeah, so if the deploy-action is configured with deploy-type
set as dags-only
then it will have the following behavior:
dags
folder - deploy-action would do a dag-only deployNote that the change has not yet been released, so you can't use it right away, but trying to get it out soon
We would like to overwrite the dag_only detection on demand. Therefore, it would be great to have a dag_only parameter.
We want to run the deploy action with the dag_only option even though we change files at a non-dags folder. Currently, we are not able to prevent the full environment build image upload.