Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How should reconfiguring CopySpecs on the Amp task work? #15

Open
vierbergenlars opened this issue May 27, 2019 · 0 comments
Open

How should reconfiguring CopySpecs on the Amp task work? #15

vierbergenlars opened this issue May 27, 2019 · 0 comments
Labels
question Further information is requested

Comments

@vierbergenlars
Copy link
Member

vierbergenlars commented May 27, 2019

There are a couple of different options.

  1. Throw away the already configured CopySpec and initialize it to a clean new one. This allows you to make complete adjustments, like you would do to a normal property; you don't have to take into account previous manipulations of the CopySpec. We have to look if it is possible to create a detached copySpec and attach it to the task's root CopySpec during task execution.
  2. Use the existing CopySpec and configure it further. This allows you to make adjustments to the CopySpec that was configured previously, but you will have to take into account previous manipulations. But that also means you can extend on the current configuration of the CopySpec (for example, to add an extra file or to add expansions)
  3. (Current situation) Create a new CopySpec for every invocation and add it to a hidden parent CopySpec. This gives you a clean environment to configure your CopySpec every time; but there is no way to remove the previously configured CopySpec, which means all files in that one will also be copied.
@vierbergenlars vierbergenlars added the question Further information is requested label Aug 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant