feat: support for Storage Boxes

[vic1707]

SUMMARY

Yesterday the new storagebox API was announced, deprecating the hrobot one in a month

It would be nice to see the hetzner.hcloud collection add support for storageboxes !

ISSUE TYPE

• Feature Idea

COMPONENT NAME

storagebox

ADDITIONAL INFORMATION

[apricote]

Hello,

thank you for your interest in the new Storage Box API.

We plan to add support for Storage Boxes to all the official integrations (like this Ansible Collection). As this involves a bit more than just adding new resources, like the new API URL api.hetzner.com, this will take a bit longer than support for other resources. We are currently in the planning phase and can not give you a guaranteed time for when Storage Box support will be available.

Kind Regards,
The Open Source Integrations team at @hetznercloud

[apricote]

We have now started working on this:

Integrating the new API

We want to make this transparent for the average user, so they do not have to think about which API URL has the resources they are interested in.

This means we want to publish the Storage Box modules next to all other existing commands:

- name: Create a basic Storage Box
  hetzner.hcloud.storage_box:
    name: Backups
    storage_box_type: bx11
    location: fsn1
    state: present

Configuring the API URL (if you want to use a proxy for example) will be done with a new base parameter api_endpoint_hetzner, in addition to the existing api_endpoint. The new argument will override the default api.hetzner.com, while the old argument overrides api.hetzner.cloud.

Progress

As this is a product that is already launched, we can work on the support in public on GitHub, as we do not want to release something half-baked we will keep a longer lived feature branch storage-boxes around until all features are ready: #676

• Add support for the new Hetzner API
• Storage Box Types
  • CRUD
• Storage Boxes
  • CRUD
  • Actions
• Storage Box Subaccounts
  • CRUD
  • Actions
• Storage Box Snapshots
  • CRUD

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.