errors when handling missing meta/main.yml

Question

errors when handling missing meta/main.yml

rl201 opened this issue 8 years ago · 4 comments

roles without meta/main.yml files seem to produce spurious dependencies. I think this is due to a mistake in scan.py around line 202:

Answer 1 · 2016-12-16T11:00:57.000Z

if not os.path.exists(self.paths["meta"]):
return ""
should perhaps be
if not os.path.exists(self.paths["meta"]):
self.dependencies=[]
return ""

Answer 2 · 2016-12-16T13:11:37.000Z

Are you saying it's reporting dependencies for the wrong role (the last role with a meta/main.yml) as is?

Answer 3 · 2016-12-16T13:35:55.000Z

Are you saying it's reporting dependencies for the wrong role as is?

Yes. If role A depends, via meta/main.yml, on role B but role B has no meta/main.yml file, role B is reported as depending on itself. Creating an empty meta/main.yml yields the expected behaviour.

Answer 4 · 2016-12-16T16:10:51.000Z

I'd happily accept a PR if you wanted to create one.