A Serverless Function in Its Own Namespace, Private, HTTP Redirected, Idling at Zero
A Scaleway Serverless Function in its own namespace, private so an IAM token is needed to invoke it (public by name), plain HTTP redirected to HTTPS, secrets in the encrypted secret variables rather than the plain ones, idling at zero instances with a ceiling you chose, and the zip archive uploaded at apply with its hash so a changed archive redeploys.
This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.
Provider drift
This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.
What depends on this
No reference architecture names this module, so changing it affects only configurations that reference it directly.
Nearest alternatives
Same cloud, same category. These are what you would weigh against it without changing provider.
The same job on other clouds
Serverless Functions on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.
Installing it
module "scaleway_function" {
source = "www.iac-bazaar.com/iac-bazaar/scaleway-function/scaleway"
version = "1.0.0"
}A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.