Ideas

Treasure Data's primary idea portal. 

Submit your ideas & feature requests directly to our product requirements team! We look forward to hearing from you.

 

Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit WM-I-18 Run digfile for Testing and Production with almost same dig file.

Workflow Test Mode Merged

Problem

Currently, we have a good way to develop a same workflow on several environments; production / staging / development.

 

Why?

When we develop a workflow, we want to change a credential and a connection info for production / staging / development.

For now. we have only 2 ways

1 - Create several same workflows to use different credential and connection info.

2 - Change a secret parameter at each situation; development -> staging -> production

But, both have cons.

1 - Difficult to maintain different workflows for each environment. And it would cause a bug.

2 - It's difficult to change a production workflow. Because we need to change a credential on production.

What we want?

We want to test/develop a workflow more easily on Sever/Local.

It would be nice if we can change development mode like Rails?.

  • Toru Takahashi
  • Mar 13 2017
  • Likely to Implement
Active Requests?
Product Component Workflow Core