We've discussed a few times storing resources somewhere that can be used by Ansible when those resources are not available publicly.
Now that I have infra access I was thinking I would do the following based on an earlier suggestion from @jbergstroem:
- create a new user on the ci machine called
resources
- generate a new keypair for that user
- have the ansible scripts render the key onto the test machines. It would have to have been extracted from the secrets repo and put into a known location by the individual running ansible
- have the ansible scripts scp the resource from the ci machine using the user
resources and the associated key
I'm still looking at alternatives but my immediate need is to get gyp onto the zOS machines. Once in place we could use it to store the resources needed for the AIX installs as well as any other similar examples
@nodejs/build what do you think ?
We've discussed a few times storing resources somewhere that can be used by Ansible when those resources are not available publicly.
Now that I have infra access I was thinking I would do the following based on an earlier suggestion from @jbergstroem:
resourcesresourcesand the associated keyI'm still looking at alternatives but my immediate need is to get gyp onto the zOS machines. Once in place we could use it to store the resources needed for the AIX installs as well as any other similar examples
@nodejs/build what do you think ?