This is an epic for implementing Hetzner cloud support.
Hetzner is the first plugin to be implemented for the first release, v0.1.0.
The reason for choosing Hetzner first is that depending on the architecture decision of Skycrane, the WASM plugins will either do HTTP calls to the API themselves or delegate that functionality to Skycrane.
Either of these means that regular SDK would not work, since inside WASI you need a special way of making http calls.
Which in turn means all SDKs need to be reimplemented to be compatible with WASI 😠and Hetzner is the least amount of work out of all the cloud providers.
Description
This plugin will create, read and delete resources on Hetzner cloud.
In order to do that, it needs to implement all the resources available via their API
Context
This is an epic for implementing Hetzner cloud support.
Hetzner is the first plugin to be implemented for the first release, v0.1.0. The reason for choosing Hetzner first is that depending on the architecture decision of Skycrane, the WASM plugins will either do HTTP calls to the API themselves or delegate that functionality to Skycrane. Either of these means that regular SDK would not work, since inside WASI you need a special way of making http calls. Which in turn means all SDKs need to be reimplemented to be compatible with WASI 😠and Hetzner is the least amount of work out of all the cloud providers.
Description
This plugin will create, read and delete resources on Hetzner cloud. In order to do that, it needs to implement all the resources available via their API
Acceptance Criteria