...
- Development environment:
- Export of flows and all dependent objects
- Import back into Development deployments for further development
- Production environment:
- Import of flows
- Import global and object-level mapping rules
- Manage releases of flows
- Rollback to previous versions as needed
- Import of flows
- APIs to manage deployments
Warning |
---|
You cannot import flows that were exported from a different edition, release, or build of the product. |
Dev/Test and Prod Deployments
...
Info |
---|
NOTE: In some cases, Dev and Test may be the same instance. |
Info |
---|
NOTE: Multiple browser tabs or windows open to different versions of the product is not supported. |
Platform instance | Description | ||
---|---|---|---|
Development (Dev) | New flows and recipes are created in a Development instance of the platform. Experiments can be undertaken without concern that production use of the recipe or flow is affected.
Rules should be established on how flows, datasets, and recipes are organized and structured. Where are these assets stored? Where are shared versions of them made available? What are the rules by which items in Dev can be moved to Test/Prod? | ||
Testing (Test) | In the Testing deployment, the objects in development are subjected to various stress tests. In the
| ||
Production (Prod) | In the Production deployment, flows and their objects are presumed to be ready for regular, read-only use. After imported flows are reconfigured for the environment, they are ready for immediate use and require no further modification.
When errors are detected, you can:
|
...
Code Block |
---|
hdfs:///mydata-prod/1/11115z4a-92f5-9f91-7v7f-g22fk99f2rru/Open_Order.csv |
To support this kind of remapping, you can specify import rules at the level of individual deployments.
Info |
---|
NOTE: For each deployment that you create, you must define new import remapping rules. |
These rules can be specified using literal values,
D s item | ||
---|---|---|
|
...