Terraform provider

fiberax/fiberax is the Terraform and OpenTofu provider for the Fiberax API: servers, SSH keys, public addresses, private networks, disks, network cards, the server firewall, backup policies and, since 0.2.0, router configuration: access rules, port forwards, WireGuard and OpenVPN tunnels with their devices; and since 0.3.0, server types with graphics cards - the cards you pick yourself, the GPU package that defines a whole machine, and the storage class of the system disk. Since 0.4.0 you can also choose the host a GPU Pro server lands on (GPU Pro is opened per project on request - see the GPU Pro guide), and since 0.4.1 the provider refuses at plan time what the platform would refuse anyway - a server with no network, no name or no credentials, an empty public_ipv4 block, two spellings of one label. Since 0.5.0 the provider follows the API rules for the server firewall and network cards at plan time (see Upgrading to 0.5) and paces itself by the rate limit the API reports in every response. 0.5.1 needs no change in your configuration: a change of ssh_keys no longer recreates the server, a server left over from an interrupted run is named on the next plan, and an unchanged firewall no longer blocks terraform destroy. 0.6.0 refuses at plan time a server order the platform would refuse (a type, image or plan that is not in the catalogue), no longer stops a server for a plan change the platform refuses anyway, and needs Terraform or OpenTofu 1.11 or later (see What is new in 0.6.0). 0.7.0 tells the platform on every terraform destroy what to do with the server's public addresses: an address taken with public_ipv4 = { new = true } goes back to the shared pool, any other stays with the project (see What is new in 0.7.0); 0.7.1 corrects the recipe for keeping such an address (see What is new in 0.7.1), 0.7.2 explains how to release only the address of a server (see What is new in 0.7.2), 0.7.3 removes false warnings from that recipe (see What is new in 0.7.3), 0.7.4 corrects the price reference (see What is new in 0.7.4), 0.7.5 gives a way out when terraform destroy stops on a server that is already gone (see What is new in 0.7.5), and 0.8.0 takes up to four backups a day, refuses at plan time more server orders the platform would refuse (limits of the type, a GPU package the type does not sell, Windows without a password, a name that is not a host name, a password with the word Administrator) and warns before a replacement that could destroy the old server and only then refuse the new one (see What is new in 0.8.0); 0.9.0 manages object storage (S3) - buckets, S3 access keys, service accounts and the storage reservation (see What is new in 0.9.0), 0.9.1 warns on the plan that replacing a server erases its data disks (see What is new in 0.9.1), 0.10.0 manages Virtual Data Center projects with an account key - ordering and closing projects, keys of one project, and working inside any project with project_id (see What is new in 0.10.0), and 0.11.0 installs SSH keys given as text on a server without adding them to the account's key pool (see What is new in 0.11.0). The current version is 0.11.0. It is in a trial period with the first customers and is not in the public Terraform registry yet, so it is served from this mirror.

What is new in 0.11.0

A new minor version: SSH keys as text come to fiberax_server. Nothing changes for an existing configuration, but ~> 0.10.0 keeps getting 0.10.0 until you change the constraint to ~> 0.11.0 (see Upgrading to 0.11).

The guide Reseller: your customers' SSH keys explains when to use text keys instead of the pool.

Upgrading to 0.11

What is new in 0.10.0

A new minor version: account keys and projects come to the provider. Nothing changes for an existing configuration, but ~> 0.9.0 keeps getting 0.9.1 until you change the constraint to ~> 0.10.0 (see Upgrading to 0.10).

The guide Projects with an account key walks through a configuration end to end.

Upgrading to 0.10

What is new in 0.9.1

A patch version: ~> 0.9.0 picks it up, and nothing changes in configurations.

What is new in 0.9.0

A new minor version: object storage (S3) comes to the provider. A configuration pinned to ~> 0.8.0 keeps getting 0.8.0 until you change the constraint to ~> 0.9.0 (see Upgrading to 0.9).

The guide Object storage (S3) walks through a configuration end to end, the aws provider for the objects included.

Upgrading to 0.9

What is new in 0.8.0

A new minor version: the plan refuses more configurations that the platform would refuse anyway. A configuration pinned to ~> 0.7.0 keeps getting 0.7.5 until you change the constraint to ~> 0.8.0 (see Upgrading to 0.8).

Every change is in the reference.

Upgrading to 0.8

What is new in 0.7.5

A patch version: ~> 0.7.0 picks it up.

What is new in 0.7.4

A patch version: ~> 0.7.0 picks it up. Only texts changed - documentation; what the provider does is the same as in 0.7.3.

What is new in 0.7.3

A patch version: ~> 0.7.0 picks it up.

What is new in 0.7.2

A patch version: only texts changed - documentation and error messages; what the provider does is the same as in 0.7.1, and ~> 0.7.0 picks it up.

What is new in 0.7.1

A patch version: only texts changed - documentation and plan error messages; what the provider does is the same as in 0.7.0, and ~> 0.7.0 picks it up.

What is new in 0.7.0

A new minor version: destroying a server now changes what happens to its public address. A configuration pinned to ~> 0.6.0 keeps getting 0.6.0 until you change the constraint to ~> 0.7.0 (see Upgrading to 0.7). Upgrade before you destroy or replace a server whose address you want to keep: the platform now releases a deleted server's public addresses by default, and 0.6.0 and earlier do not tell it otherwise.

Upgrading to 0.7

What is new in 0.6.0

A new minor version: a configuration pinned to ~> 0.5.0 keeps getting 0.5.1 until you change the constraint to ~> 0.6.0 (see Upgrading to 0.6). It is a minor version because the provider now refuses more at plan time.

Known limitation. A disk written by 0.5.1 or imported has no record of the size the provider applied. Until the provider changes that disk once, reducing its size_gb in the configuration gives a plan-time warning that says the disk was grown outside Terraform (0.5.1 refused the plan); the apply then fails on that disk and changes nothing on it, while other resources of the run are applied. A disk can only grow.

Upgrading to 0.6

Upgrading to 0.5

0.5.0 changes what some configurations must say, so it is a new minor version: a configuration pinned to ~> 0.4.0 keeps getting 0.4.1 until you change the constraint to ~> 0.5.0. Two things to check before you do:

Both show up as an error on terraform plan, before anything is changed - the firewall one on a plan that creates or changes the firewall. Since 0.5.1 a firewall written under 0.4 and left unchanged plans and destroys as it is; name the policies the next time you edit it.

The normal way: let Terraform download it

Add nine lines to your Terraform or OpenTofu configuration file and terraform init fetches the provider from here with a verified checksum. The lines, the example and the one warning you will see are in Getting started, section 7.

Reference

Every resource and data source with its fields, examples and import syntax: Terraform provider reference.

Direct downloads

Each archive contains one file, the provider binary terraform-provider-fiberax_v0.11.0.

Checksums of all archives: terraform-provider-fiberax_0.11.0_SHA256SUMS.

Earlier versions

Versions 0.10.0, 0.9.1, 0.9.0, 0.8.0, 0.7.5, 0.7.4, 0.7.3, 0.7.2, 0.7.1, 0.7.0, 0.6.0, 0.5.1, 0.5.0, 0.4.1, 0.4.0, 0.3.0, 0.2.0 and 0.1.0 stay on the mirror for configurations and lock files that pin them, and Terraform fetches them the usual way; new configurations should use 0.11.0. To download one by hand, archives are named terraform-provider-fiberax_<version>_<os>_<arch>.zip under /terraform/mirror/archives/, with the same platforms as above. Checksums:

Manual installation

If you prefer not to use the mirror settings, put the archive for your platform into Terraform's local plugin directory, unchanged, under its registry path - for example on Linux:

~/.terraform.d/plugins/registry.terraform.io/fiberax/fiberax/terraform-provider-fiberax_0.11.0_linux_amd64.zip

On Windows the directory is %APPDATA%\terraform.d\plugins\; OpenTofu reads the same layout under registry.opentofu.org/. Terraform picks the provider up from there on init without any further configuration.

Mirror index files for tools live under registry.terraform.io/fiberax/fiberax/ and registry.opentofu.org/fiberax/fiberax/. Something not working? Write to us and quote what terraform init printed.