nirvana-labs/terraform-provider-nirvana v1.47.0 on GitHub

1.47.0 (2026-05-11)

Features

api: add autoscaling field to nks_cluster (ef368e5)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

Greptile Summary

This automated release PR bumps the provider version to 1.47.0 and adds an autoscaling boolean field to the nirvana_nks_cluster resource and its associated data sources, reflecting a new field in the upstream API spec.

Resource schema: autoscaling is added as Required on the nirvana_nks_cluster resource. This is a breaking change for any existing consumer — all current .tf configs must add the attribute or fail validation after upgrading.
Data sources: autoscaling is correctly added as Computed on both the single-cluster and list data sources, which is non-breaking.
No plan modifier on autoscaling in the resource schema, implying the API supports in-place toggling without recreating the cluster.

Confidence Score: 4/5

The data source changes are safe. The resource change adds a Required field to an existing resource type, which will break any existing consumer config on upgrade.

Introducing autoscaling as Required on an already-published nirvana_nks_cluster resource means every user who upgrades to 1.47.0 without updating their .tf files will immediately hit a validation failure. Making the field Optional (or Optional+Computed) would let existing configs continue working while still exposing the new capability.

internal/services/nks_cluster/schema.go — the Required designation on the new autoscaling attribute is the sole concern.

Important Files Changed

Filename	Overview
internal/services/nks_cluster/schema.go	Adds `autoscaling` as a Required BoolAttribute — this is a breaking change for existing users of the resource who must now update all existing configs.
internal/services/nks_cluster/model.go	Adds `Autoscaling types.Bool` field tagged as `json:"autoscaling,required"` — consistent with schema.go.
internal/services/nks_cluster/data_source_schema.go	Adds `autoscaling` as Computed BoolAttribute on the single-cluster data source schema — correct.
internal/services/nks_cluster/list_data_source_schema.go	Adds `autoscaling` as Computed BoolAttribute inside the list data source items — correct.
internal/version.go	Version constant bumped from 1.46.0 to 1.47.0.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User upgrades to v1.47.0] --> B{Has existing nirvana_nks_cluster resource?}
    B -- No --> C[Add autoscaling = true/false to new config]
    B -- Yes --> D{Config includes autoscaling?}
    D -- Yes --> E[terraform plan succeeds]
    D -- No --> F[❌ terraform validate fails - autoscaling is required]
    C --> E
    E --> G[API call includes autoscaling field in create/update body]
    G --> H[In-place update supported - no RequiresReplace modifier]

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.