• 1 Post
  • 49 Comments
Joined 2 years ago
cake
Cake day: June 4th, 2023

help-circle





  • It uses USB-C for the charging cable. The cable between the headset and power supply is a locking proprietary connector, discussion on hackers news indicates it’s because USB-C locking connectors are not elegant and it has specific power requirements so using it with a random cable and random battery pack is not a good idea. The “battery pack” is also the power supply for the processor, it’s not really locking into a proprietary cable any more than it’s locking you into a proprietary operating system. Saying either of those is essentially meaningless to the discussion of the device.




    • Dynamic inventory. I haven’t used it on a cloud api before but I have used it against kube API and it was manageable. Are you saying through kubectl the node names are different depending on which cloud and it’s not uniform? Edit: Oh you’re talking about the VMs doh

    • I’ve tried ansible vault and didn’t make it very far… I agree that thing is a mess.

    • Thank god I haven’t ran into interpreter issues, that sounds like hell.

    • Ansible output is terrible, no argument there.

    • I don’t remember the name for it, but I use parameterized template tasks. That might help with this? Edit: include_tasks.

    • I think this is due to not a very good IDE for including the whole scope of the playbook, which could be a condemnation of ansible or just needing better abstraction layers for this complex thing we are trying to manage the unmanageable with.