Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

How to separate test and production?

What's the best, or at least a good, practice for separating development/test setups from production? We're using one Matillion instance.

Some ideas
1) make a locked version 'Production' of the project, and do further development and testing in the default version

2) separate environments 'production' and 'test' that use different default schemas. All development, test and temporary views go to a temp schema, and only productive target tables to the production schema that will be backed up

3) create separate projects 'test' and 'production'

We've done 1) and 2). To do 3), we'd like to copy the tested version of processes from test to production. However, when we do Export & Import, we'll just get duplicate processes into the same, existing project. Is there a way to import as a new project?

1 Community Answers

Matillion Agent  

Ian Funnell —

Hi Arto,

All of the approaches you’ve outlined are perfectly valid, and have been successfully used by various customers.

It’s best for you to choose whichever processes matches most closely onto your organisation’s current procedures concerning development, testing and software release.

You have two main options for code promotion:

If you need to Import into a new project you’ll have to create it first and switch to it. Import can’t create a new project on its own.

In contrast, the POST operation can create a new project, although it will not overwrite one that already exists.

Best regards,
Ian

Post Your Community Answer

To add an answer please login