stackit-dev-tools/terraform-provider-stackitprivatepreview
2
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

Reference Migration Guide in README (#18)

Browse source 
* Reference Migration Guide in README

* Adjust phrasing

Co-authored-by: Vicente Pinto <vicente.pinto@freiheit.com>

---------

Co-authored-by: Vicente Pinto <vicente.pinto@freiheit.com>
This commit is contained in:
João Palet 2023-09-12 16:05:34 +02:00 • committed by GitHub
parent 78dcc66e5e
commit 41d534a5b5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
MIGRATION.md
View file

@ -1,6 +1,6 @@
# Migration from the Terraform community provider
# Migration Guide
In this guide, we want to offer some strategy for a migration of configurations from the [Terraform community provider](https://github.com/SchwarzIT/terraform-provider-stackit) to this new official provider. In this provider, some attribute names and structure have changed, as well as the internal resource ID structure.
In this guide we want to offer some strategy for a migration of configurations or existing resources to the STACKIT official provider. In relation to the [Terraform community provider](https://github.com/SchwarzIT/terraform-provider-stackit), some attribute names and structure have changed, as well as the internal resource ID structure.
To import your existing infrastructure resources to the new provider, you'll need the internal ID of each resource. The structure of the new provider's internal ID can be located in the [documentation](./docs/resources) file for each resource, specifically within the description of the `id` attribute.

7
README.md
View file

@ -10,7 +10,7 @@ Check one of the examples in the [examples](examples/) folder.
Currently, only the *token flow* is supported. The Terraform provider will first try to find a token in the `STACKIT_SERVICE_ACCOUNT_TOKEN` env var. If not present, it will check the credentials file located in the path defined by the `STACKIT_CREDENTIALS_PATH` env var, if specified, or in `$HOME/.stackit/credentials.json` as a fallback. If the token is found, all the requests are authenticated using that token.
## Acceptance tests
## Acceptance Tests
Terraform acceptance tests are run using the command `make test-acceptance-tf`. For all services,
- The env var `TF_ACC_PROJECT_ID` must be set with the ID of the STACKIT test project to test it.
@ -25,7 +25,10 @@ Additionally, for the Resource Manager service,
**WARNING:** Acceptance tests will create real resources, which may incur in costs.
## Reporting issues
## Migration
For guidance on how to migrate to using this provider, please see our [Migration Guide](./MIGRATION.md).
## Reporting Issues
If you encounter any issues or have suggestions for improvements, please open an issue in the repository.
## Contribute