Right, It's nothing different than ansible. I don't know ansible and I don't want to depend on any other tool while developing onctl. But would be nice to implement something to support. What I did already is to be able to export for ansible and puppet (similar to kubectl -o parameter ex. onctl ls -opuppet) configuration to be able to use it later on. But with integrating, that will require user to have experience about the other tool and also need to configure that as well. Also wouldn't be possible to achieve the end result with single command.
About the license on onctl-templates.. I defined it as MIT, which I assume should be OK with everybody.
Actually we're aware that it's not clearly defined. Build on top of a nice infrastructure, we're playing with the positioning of the product by having more feedback. Trying to find a nice spot :)
About the license on onctl-templates.. I defined it as MIT, which I assume should be OK with everybody.