Skip to content

Commit

Permalink
no need to touch Terraform state during migration (#405)
Browse files Browse the repository at this point in the history
* no need to touch Terraform state during migration

* update Migration guide, recommend v1.2 or higher
  • Loading branch information
davidbloss authored Jul 15, 2024
1 parent 008f156 commit 64b0c2c
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions MIGRATION.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,12 @@
# Migration Guide to v1.0.0

For everyone upgrading from a version before v1.0.0, we recommend upgrading straight to v1.2 or higher.

We at OpsLevel have been working on upgrading [our Terraform provider](https://github.com/OpsLevel/terraform-provider-opslevel) to version 1.0.0.

While the majority of these improvements are under the hood, there are a few Terraform configuration changes to be aware of.

For errors encountered during `terraform apply`, see the [State Migration](#state-migration) section below.
For errors encountered during `terraform apply`, see the [State Migration](#state-migration) section below - Applies only to v1.0.0 up to v1.1.x

# BREAKING CHANGES to some resource fields

Expand Down Expand Up @@ -169,7 +171,9 @@ Changes to Outputs:
]
```

# State Migration
# State Migration (Applies to v1.0.0 up to v1.1.x)

We recommend upgrading straight to v1.2 or higher. But for versions between v1.0.0 and v1.1.x, the following may be needed.

The structure of some resource data has changed from v0.11.0 to v1.0.0.
If you encounter erros like `Error: Unable to Read Previously Saved State for UpgradeResourceState`
Expand Down

0 comments on commit 64b0c2c

Please sign in to comment.