Skip to main content

Revisit the name of the predelivered Execution Environment in Migrate

Syniti Knowledge PlatformMigrateReplicate

Currently, it is predelivered with the name DEV (Development), it may be better be named as “Default” or similar?

I understand that it is editable but renaming was not recommended in a Support request.

Posted by Ana Garcia Rubio (Syniti) ·
Status: Unlikely to Implement3 comments

Log in to comment and vote

Comments3

  • John Munkberg

    Team•

    Feb 22

    @Ana Garcia Rubio (Syniti) I’m confused on this one. Default doesn’t really convey anything.

    In a single tier environment - what would this be called. It’s DEV because this is where ALL of the rules, reports, etc are developed for the first time. This is where all the work happens. It’s messy, its development.

    When we get more rigid and start to move into multi-tier environments - then you have DEV / LOAD (LOAD because the purpose of this second environment to execute a MOCK LOAD and leave your data static for the duration of the Mock Load cycle - allowing you to continue to DEVELOP new changes in DEV.

    In some (not recommended) cases - we can multiple Tiers (DEV / QA / PROD) - but QA and PROD do not make much sense in the process of Data Migration….. All data is PROD data, and what really changes where you LOAD the data ( as you know). So it’s struggle to call an ETL rule a PROD rule?

    Other uses cases are for CLEANSING environments - DEV / CLEANSE / LOAD - in the case a LOAD runs for several weeks but you want to collect CLEANSING metrics weekly, for example.

    I think the BEST CASE is to make sure (via effective testing) that you are free to RENAME DEV to be anything you want. The DEFAULT Flag is supposed to dictate the functionality of the code, not the NAME of the environment.

    If you change the name - everything SHOULD work just fine. If it doesn’t, that is a BUG in the software. That is exactly why we didn’t rely on the NAME, but instead added the “Default” flag.

    I have submitted a SUPPORT ISSUE to verify that the functionality works as intended, or to fix it if it doesn’t work (per the support recommendation).

    • Ana Garcia Rubio (Syniti)

      •

      Feb 23

      Thanks John, it’s always helpful to have your perspective and we are aligned on the DEV / LOAD concept.

      This question has been raised by several projects that load from the default environment, keeping the implementation ready for the mock loads i.e. not promoting. This would be similar to a single ADM setup.

      FYI this is the request where renaming was not advised (#128252)


  • John Sanders

    •

    Jan 14

    Thanks Ana. We have received similar requests around adding flexibility to the working environments/development areas. I will include your feedback.