ansible / galaxy-dev

Ansible Automation Hub

11 stars 13 forks source link

Story: Sandboxing the importer #194

Closed chouseknecht closed 4 years ago

chouseknecht commented 4 years ago

Problem:

[ ] Isolate the custom Collection code during static analysis and ansible-test, such that there can be no root access and no outbound network connections
[ ] Execute on OpenShift and a standalone VM
[ ] be able to inject custom configuration for any lint and test tools

chouseknecht commented 4 years ago

122 - @awcrosby

@bmbouters will be working on the following:

Investigate with the pulp_container team to add functionality for building an image from a Dockerfile. We're told the pieces for executing a build are mostly there, and image build is on the roadmap.

@cutwater

Will help @awcrosby abstract the "runner" layer such that it's pluggable and could run the importer via Jenkins job, OpenShift job, docker run, maybe a Tower Job, etc.

chouseknecht commented 4 years ago

222 is part of this story. Once we're able to run `ansible-test` and capture the output, we need to surface it in the UI. It will automatically show up on My Imports, but it needs to be added to Content Details for a given collection version.

awcrosby commented 4 years ago

ansible-test sanity is now deployed on production, running in separate jobs in a separate service set.

ansible / galaxy-dev

Story: Sandboxing the importer #194

122 - @awcrosby

222 is part of this story. Once we're able to run ansible-test and capture the output, we need to surface it in the UI. It will automatically show up on My Imports, but it needs to be added to Content Details for a given collection version.

222 is part of this story. Once we're able to run `ansible-test` and capture the output, we need to surface it in the UI. It will automatically show up on My Imports, but it needs to be added to Content Details for a given collection version.