Error: output directory is not empty!

[casperdcl]

following #340:

resource "iterative_task" "task" {
  ...
  workdir { input = "${path.root}/shared" }
}

results in Error: output directory ./shared is not empty!

We should support having output == input. It may cause edge cases/issues, but we should fix said issues later. To an end-user, output=input is a basic use case (default assumption for any pipeline). It's better to document/add FAQs for now saying "use output!=input to fix your problems."

[0x2b3bfa0]

This behavior seems intentional and especially counterintuitive.

terraform-provider-iterative/iterative/resource_task.go

Lines 287 to 289 in be9e0cd

	if directory_out == "" {
	directory_out = directory
	}

[casperdcl]

Yes there's nothing wrong with effectively if not output: output = input but the problem is subsequently insisting that output.ls() == []

[DavidGOrtega]

Im not following this.
If the output dir exists and is not empty it fails to not overwrite it (and to not upload it also at start).
Whats the issue? what's counterintuitive?

[0x2b3bfa0]

🤔 If output has to be empty, it would make more sense to remove the code mentioned on #358 (comment).

[0x2b3bfa0]

Using the same directory for input and output is known to produce all kinds of issues. Should we support this mode of operation?

[DavidGOrtega]

Using the same directory for input and output is known to produce all kinds of issues. Should we support this mode of operation?

For one task is OK, errors comes with more than one task def or reusing the task

[DavidGOrtega]

I have created a fix, the order was not right. Now sets the output as the input if not defined and verifies the output to be OK if defined