Enonic dump operations do not work on remote hosts

[gbbirkisson]

It tries to read some local directories that are not present instead of calling the remote XP server.

$ enonic dump ls
Error reading dumps folder: open data/dump: no such file or directory

[alansemenov]

@gbbirkisson You have set environment variables, right?

[gbbirkisson]

Yes I have.

All dump operations use this function ensureNameFlag:

cli-enonic/internal/app/commands/dump/dump.go

Lines 23 to 24 in 14833d5

	func ensureNameFlag(name string, mustNotExist, force bool) string {
	existingDumps := listExistingDumpNames()

And that function never calls the remote server:

cli-enonic/internal/app/commands/dump/list.go

Lines 30 to 44 in 14833d5

	func listExistingDumpNames() []string {
	homePath := sandbox.GetActiveHomePath()
	dumpsDir := filepath.Join(homePath, "data", "dump")
	dumps, err := ioutil.ReadDir(dumpsDir)
	if err != nil {
	util.Warn(err, "Error reading dumps folder:")
	return []string{}
	}
	dumpNames := make([]string, len(dumps))
	for i, dump := range dumps {
	dumpNames[i] = dump.Name()
	}
	return dumpNames
	}

[pmi]

It tries to read some local directories that are not present instead of calling the remote XP server.

$ enonic dump ls
Error reading dumps folder: open data/dump: no such file or directory

XP remote API simply does not have list command cuz there is no way for it can list local dump files.
So CLI is just being clever and just scans the local folder for previous dumps.