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

Explicit dependencies fail inside of case statements #385

Closed
rebeccaskinner opened this issue Oct 17, 2016 · 1 comment
Closed

Explicit dependencies fail inside of case statements #385

rebeccaskinner opened this issue Oct 17, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@rebeccaskinner
Copy link
Contributor

This is broken:

file.content "foo" {
  destination = "foo"
  content = "foo"
}

switch "touch-file" {
  default {
    task.query "touch-file" {
      query = "touch file.txt"
      depends = ["file.content.foo"]
    }
  }
}

Probably because dependency resolution isn't addressing ancestor nodes for explicit dependencies, we should probably look at the code that's being used by lookup and param dependency generation and either put that in getDepends or move the logic to the actual walk function.

@rebeccaskinner
Copy link
Contributor Author

Closed by #391

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants