avass[m] | zbr: is it not possible to use requirements.yaml for collections in ansible-galaxy? | 14:40 |
---|---|---|
fungi | if ansible-galaxy collections are published to pypi | 15:03 |
avass[m] | that's a bit weird | 15:03 |
fungi | i don't know that much about ansible-galaxy collections, but requirements.yaml is a list of python packages published on pypi, so if ansible-galaxy collections are published to pypi then it might make sense to list them in requirements.yaml | 15:04 |
fungi | if they're not published to pypi, then probably some other listing mechanism is needed | 15:05 |
avass[m] | ah I think I just had the wrong syntax | 15:10 |
avass[m] | I was reading: https://galaxy.ansible.com/docs/using/installing.html#dependencies | 15:11 |
avass[m] | but apparently I needed to do: https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#install-multiple-collections-with-a-requirements-file | 15:11 |
corvus | masterpe: I have a theory about your mod status: it looks like you joined this portal room in August 2020. It's possible that no one was in the OFTC channel during that time, and OFTC auto-op'd you, so Matrix set you as mod. You then left, and rejoined a couple of days ago, and Matrix had retained your mod status from earlier. | 15:31 |
corvus | i'm at least happy enough with that theory that i don't think we need to preserve the state for any more debugging, and i think we can go ahead and de-mod you | 15:33 |
*** ChanServ sets mode: +o masterpe[m] | 15:33 | |
*** ChanServ sets mode: -o masterpe[m] | 15:34 | |
corvus | infra-root: ^ fyi | 15:34 |
fungi | corvus: it's just moderator status in the matrix room, right? on oftc there's no chanop on the nick | 15:42 |
fungi | at least not any longer | 15:42 |
corvus | hrm, zuul-registry has failed changes 4x with this error: https://zuul.opendev.org/t/zuul/build/c38fef9eb6fc4c7dabe3e66a307eac65 : Task Add project atomic PPA failed running on host ubuntu-focal: apt cache update failed | 15:43 |
corvus | fungi: correct | 15:43 |
corvus | fungi: to correct, i told chanserv to op masterpe[m] to get them in sync, then deop masterpe[m] to remove ops on both sides. | 15:44 |
opendevreview | James E. Blair proposed zuul/zuul-registry master: Test https://review.opendev.org/c/zuul/zuul-registry/+/797179 | 15:46 |
fungi | cool | 15:46 |
avass[m] | is this all there is to registry.yaml or is it possible to put user/pass in a separate file? https://review.opendev.org/c/zuul/zuul-registry/+/788389/5/playbooks/functional-test/restricted/conf/registry.yaml | 15:50 |
fungi | avass[m]: oh! i just realized you said requirements.yaml, i was thinking of requirements.txt | 15:51 |
fungi | sorry | 15:51 |
avass[m] | np :) | 15:51 |
fungi | i know absolutely nothing about requirements.yaml files, so ignore anything i said ;) | 15:52 |
avass[m] | now I just have to figure out how to bootstrap zuul-registry in k3s to use a version that's not released yet, since I don't care about tls when it's on my LAN... https://review.opendev.org/c/zuul/zuul-registry/+/788390 :) | 15:55 |
opendevreview | James E. Blair proposed zuul/zuul master: Use create_all for empty databases https://review.opendev.org/c/zuul/zuul/+/797180 | 18:03 |
corvus | i thought that would save time in tests, but it does not :/ | 18:03 |
corvus | avass: that's all there is to registry.yaml ; no external file support | 18:27 |
avass[m] | I think nodepool could benefit from a kubevirt driver :) | 18:33 |
masterpe[m] | corvus nice that it is clearifyed. | 19:47 |
tristanC | avass[m]: with https://review.opendev.org/c/zuul/zuul-registry/+/788390 you can have user/pass in environment | 20:57 |
tristanC | avass[m]: actually the change supporting %(..) syntax is already merged | 20:58 |
avass[m] | ah: https://review.opendev.org/c/zuul/zuul-registry/+/710886 | 20:58 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!