I believe there were some discussions in the past, but nothing materialized out of it.
Such functionality would of course be welcome in Libcloud. It's worth noting that implementing a new API in Libcloud requires implementing drivers for at least 3 different providers / implementations. This way it's less likely for the standard API to be biased against a single provider / implementation. On Sun, Nov 8, 2020 at 4:30 PM Taras Shapovalov <shapovalo...@gmail.com> wrote: > Hello, > > I was surprised to find out that creation of resources with a single > template like OpenStack Heat or AWS CloudFormation is not only unsupported > in libcloud, but I also did not find any discussions or maillist questions > about that. I was thinking of trying to implement the Heat support (at > least to start with it), but I feel like there is a fundamental obstacle > that I miss. Can someone please tell me what is a state of such > functionality in libcloud or point me to an already existent discussion? > > Best regards, > > Taras >
