Import/Export scenarios: When is a password required?
The following section describes which of the various export/import scenarios require a password to be specified.
In all scenarios, if you import a project to an existing project, the credentials of the existing projects are preserved (as they are part of the project configuration).
Scenario 1: Moving a project or project configuration between two Compose machines without retaining the project credentials. This is useful when importing to a new project that will have different project credentials.
In such a scenario, simply add the is_without_credentials parameter to either the export or the import command.
Scenario 2: Moving a project or project configuration between two Compose machines that have the same Master User Password.
In such a scenario, neither the export command nor the import command need to include a password. If you do not want the source and target projects to have the same credentials (for Data Zone connectivity, etc.), then you also need to specify the is_without_credentials parameter in either the export or the import command.
Scenario 3: Moving a project or project configuration between two Compose machines that have a different Master User Password, but without revealing the Master User Password of the source machine.
In such a scenario, the export command must include the password and master_user_password parameters while the import command must include the password parameter. The same password (specified with the password parameter) must be used for both export and import.
Scenario 4: Moving a project or project configuration between two Compose machines that have a different Master User Password.
In such a scenario, the export command does not need to include a password, but the import command should specify the Master User Password of the source machine (using the password parameter).