Create Migrate Command

[dylanyoung-dev]

Need to be able to migrate configuration from one CDP/Personalize Tenant to another. The big question though, is that there really needs to be rules to determine what gets migrated. The command really should be configured to run in an automated fashion, to migrate content from one tenant to another in an automated fashion every 24 hours or something like that. This is where things get a little complicated. This should really only migrate content and not configuration, especially if the team is using this tool to handle deploys. However as previously mentioned, the goal is to not restrict users, and there could be users manually running this process or running the process without deploys and they want the ability to migrate a full tenant to another tenant.

The only way to really handle those scenarios is to have this have some form of configuration, maybe a init process to create the config and then some form of config.yaml/json that sits in the root of the site with specific instructions to the migrate command. Likely this is handled by a manual process or in a CI/CD process to automate the sync.