Daniel Goldman

@s-hertel would you be able to re-review this?

looks like a flaky CI? I don't think this would affect the galaxy setup looks like this hung: ``` 03:53 TASK [ansible-galaxy-collection : setup test collections for install and download...

I was going to work on this, but there's already a little error popup. If not installed: ``` Command failed: ansible-lint --offline --nocolor -f codeclimate "/tmp/vsc/playbook.yml" /bin/sh: 1: ansible-lint: not...

Right. Seems like that was a fix for #20 , where the problem was pip 10.0.0 . Seems that pip 10.0.0 changed its internals; but, since it was installed by...

I've been diffing the versions in the 2 repos, making sure all the other files are the same, and I've found some differences that I wasn't sure we wanted to...

oh neat, I didn't know about the (upcoming) `--chmod`, that's cool. We could also change the permission of the files _outside_ the container. thoughts? I can combine the COPY instructions...

> > We could also change the permission of the files outside the container. thoughts? > > That would not have any effect on the resulting file inside the container...

sorry folks, are we waiting on me for something on this?

So, doing a bit of an overview of the applicability for boilerplate reduction: generating lockfile (searched GeneratePythonLockfile): - 19 are pure boilerplate (`return GeneratePythonLockfile.from_tool(..., use_pex=python_setup.generate_lockfiles_with_pex)`) - 6 are slightly advanced...

Relating to integration testing, that's really interesting. I wonder if the real boilerplate is in the tests, rather than the code. Obviously, any tool defined through metalint has that boilerplate...