Bradley A. Thornton
Bradley A. Thornton
That capability doesn't exist today, but I see why that would be useful. I'd have to crack open the code, which I won't have time to do for a while....
Currently no. The trig gets tricky. What I've done is simply put the physical names in the lables... Po4 ( eth1/4, eth 1/5) would that work ?
The labels should be sized to fit within the space they have. Do you have an example yaml?
or XDG_DATA_HOME since the files don't really need to be "cached" for use by navigator later: https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
We need to be sure 2 instances of navigator don't collide after the navigator provided UUI in the path is gone
Good idea, this would probably be exposed as an additional subcommand which ran galaxy for the user. Will be looked at closer later this year.
Example: ``` collections: pull: policy: - force (ansible-galaxy collection force) - missing (ansible-galaxy collection install) - never (do nothing) - upgrade (ansible-galaxy collection upgrade) ``
Will need to check what the default behaviour of controller/AWX is, I'm assuming it is "missing", being it will collect anything not present, but not upgrade anything that is... I'm...
@ssbarnea Have you done anymore research here to see what changes may be required? Does setting the pull-policy to never help at all?