Metl is a simple, web-based integration platform that allows for several different styles of data integration including messaging, file based Extract/Transform/Load (ETL), and remote procedure invocation via Web Services. Read more at www.jumpmind.com/products/metl/overview
GNU General Public License v3.0
208
stars
82
forks
source link
When deploying a flow only associated models and resources should be deployed not all in a project #919
When deploying a flow that either has several resources in its own project or belongs to a project that has a project dependency referring to a common model or resource project with several models or resources, currently all models or resources in the dependent project get deployed even if the flow only references a couple. Should we only deploy just the associated models and resources tied to the flow being deployed? This would help with license tracking as well.
For example: Flow F1 in Project P1 has a project dependency of project P2. P2 has 10 resources. Flow F1 only uses 2 resources from within P2 but when you deploy flow F1 it deploys all 10 resources.
When deploying a flow that either has several resources in its own project or belongs to a project that has a project dependency referring to a common model or resource project with several models or resources, currently all models or resources in the dependent project get deployed even if the flow only references a couple. Should we only deploy just the associated models and resources tied to the flow being deployed? This would help with license tracking as well.
For example: Flow F1 in Project P1 has a project dependency of project P2. P2 has 10 resources. Flow F1 only uses 2 resources from within P2 but when you deploy flow F1 it deploys all 10 resources.