how to organize the environements & projects in data productivity cloud , we want data load from source to QA but move the pipeline to prod , but when we move the jobs to PROD the configs have to change dynamically rather than i see it still require code change
have 2 projects 1 for qa , another for production , Pipeline will be developed and smoke test in QA then moved to another project , any way to automate the process rather than export and import of code ? how does really environments work when there are only one projects becase if i want to test something these can't be done ?
Hey @venu.mashetty 👋 Welcome to the Matillion Community!
Apologies for the delay in responding; I've been chatting about this internally as we (@JoeCommunityManager and I) think it's something we can provide further assistance on! We're planning a blog on this, as it has come up a few times with prospects, customers and partners alike.
Likely, you don't want a distinct `project` for QA/production but separate via environments. You might find the existing documentation helpful here, https://docs.matillion.com/data-productivity-cloud/designer/docs/projects/ or we can have a call to discuss what you are trying to accomplish, https://bit.ly/m/johnathanlaw.
As noted here, https://docs.matillion.com/data-productivity-cloud/designer/docs/variables/#creating-variables, you can use different default values for variables between environments - which might assist with what you're trying to do.
Look forward to hearing back from you,
Johnathan