Add instance:export and instance:download command

[SGD1953]

It would be great if sfcc-ci would allow to transfer one sandbox' state to another, therefore commands to run a site export & download it would be desirable.

[tobiaslohr]

Proposal:

Two additional commands (see below), should be tracked as separate issues. Once they are done, we can think about providing a high level command to copy an instance (propose to limit to sandbox only) which makes use of

New Command 1:

sfcc-ci instance:export --instance <instance> --data-units <units> --export-file <file> --sync

Options:

--instance optional, being the host name of the instance,
--data-units being the set of data in JSON format to export
--export-file being the file to store exported data to on the instance, relative to impex/src/instance
--sync optional, whether to run in sync mode

New Command 2:

sfcc-ci data:download --instance <instance> --source <target> --file <file>

Options:

--instance optional, being the host name of the instance, e.g.
--file being the file to download from instance and
--source being the source location on the instance to download from relative to /webdav/Sites/Impex/, e.g. "src/instance"

[SGD1953]

Love it, would only update to sfcc-ci data:download --instance <instance> --source <WebDAV folder> --file <file>. Also why do we separate file & folder?

[tobiaslohr]

Love it, would only update to sfcc-ci data:download --instance --source --file

Shall source be relative to /webdav/Sites/Impex/ or relative to /webdav/Sites/

Also why do we separate file & folder?

Just a proposal right now to be somewhat consistent with #30. Thoughts?

[SGD1953]

Here is what we have:

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Cartridges - does code download make sense? Probably not so much.

Log Files

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Logs - makes sense to download, maybe we need some more syntactic sugar to i.e. download logs for a day.

Security Log Files

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Securitylogs -see above

Import/Export

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Impex - covered

Temp

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Temp - would be covered if relative to Sites

Realm Data

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Realmdata - would be covered if relative to Sites

Organization Static Content

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Static - would be covered if relative to Sites

Catalog

https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Catalogs/[Catalog name] - would be covered if relative to Sites

Content Images
https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Libraries/[Library Name] - would be covered if relative to Sites

Velocity Templates
https://dgehl-inside-eu01-dw.demandware.net/on/demandware.servlet/webdav/Sites/Dynamic/[Site Name], for example SiteGenesis. - would be covered if relative to Sites

So in my view, yes, relative to Sites would work. Maybe we should separate the root location out into a separate parameter so that we can more easily validate if it is supported.

[tobiaslohr]

We are splitting this into two tickets for better visibility.

1. instance:export command to run an instance export instance:export command to run an instance export #121
2. data:download command to download resources Add data:download command to download resources #122