Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix broken links in migration docs #476

Merged
merged 2 commits into from Sep 13, 2022
Merged

Fix broken links in migration docs #476

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1be92c8
fix broken link in "Testing Migration" section
bookshelfdave Sep 12, 2022
193e3f6
fix broken links on framework/migrating/schema page
bookshelfdave Sep 12, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
3 changes: 2 additions & 1 deletion website/docs/plugin/framework/migrating/index.mdx
View file
Open in desktop
Expand Up @@ -28,7 +28,8 @@ Refer to the [Combining and Translating documentation](/plugin/mux) for details

## Testing Migration

As you complete the migration, we recommend that you follow Test Driven Development by writing tests to ensure that the migration does not affect provider behavior. Refer to [Testing Migration](/plugin/framework/migrating/testing/testing#testing-migration) for details and an example.
As you complete the migration, we recommend that you follow Test Driven Development by writing tests to ensure that the migration does not affect provider behavior. Refer to [Testing Migration](/plugin/framework/migrating/testing#testing-migration) for details and an example.


## Migration steps

Expand Down
16 changes: 8 additions & 8 deletions website/docs/plugin/framework/migrating/schema/index.mdx
View file
Open in desktop
Expand Up @@ -11,14 +11,14 @@ constraints of Terraform configuration blocks and how the provider, resource, or
[Schemas](/plugin/framework/schemas) in the Framework documentation for details.

This page explains the differences between the schema used by SDKv2 and the Framework. We also recommend reviewing these additional schema guides throughout the migration:

- [Attributes](/plugin/framework/migrating/attribute-blocks/attribute-schema) where the schema defines practitioner or provider data associated with a value and type.
- [Attribute types](/plugin/framework/migrating/attribute-blocks/types) where the schema defines the expected data structure and syntax.
- [Attribute fields](/plugin/framework/migrating/attribute-blocks/fields) where the behaviors of an attribute are defined, such as `Required`, `Optional`, `Computed`, and `Sensitive`.
- [Attribute defaults](/plugin/framework/migrating/attribute-blocks/default-values) where the schema defines a value for an attribute which should be automatically included in a Terraform plan if it is not configured by the practitioner.
- [Attributes without in-place updates](/plugin/framework/migrating/force-new) where the schema defines an attribute that requires resource replacement if the value is updated.
- [Attribute predefined validations](/plugin/framework/migrating/attribute-blocks/validators-predefined) and [custom validations](/plugin/framework/migrating/attribute-blocks/validators-custom) where the schema defines the syntax, constraints, or encoding expectations of a value.
- [Blocks](/plugin/framework/migrating/attribute-blocks/attribute-schema) and [computed blocks](/plugin/framework/migrating/attribute-blocks/blocks-computed) where the schema defines structural configuration sections of data, typically with nested attributes or further blocks.
/attributes-blocks/
- [Attributes](/plugin/framework/migrating/attributes-blocks/attribute-schema) where the schema defines practitioner or provider data associated with a value and type.
- [Attribute types](/plugin/framework/migrating/attributes-blocks/types) where the schema defines the expected data structure and syntax.
- [Attribute fields](/plugin/framework/migrating/attributes-blocks/fields) where the behaviors of an attribute are defined, such as `Required`, `Optional`, `Computed`, and `Sensitive`.
- [Attribute defaults](/plugin/framework/migrating/attributes-blocks/default-values) where the schema defines a value for an attribute which should be automatically included in a Terraform plan if it is not configured by the practitioner.
- [Attributes without in-place updates](/plugin/framework/migrating/attributes-blocks/force-new) where the schema defines an attribute that requires resource replacement if the value is updated.
- [Attribute predefined validations](/plugin/framework/migrating/attributes-blocks/validators-predefined) and [custom validations](/plugin/framework/migrating/attributes-blocks/validators-custom) where the schema defines the syntax, constraints, or encoding expectations of a value.
- [Blocks](/plugin/framework/migrating/attributes-blocks/attribute-schema) and [computed blocks](/plugin/framework/migrating/attributes-blocks/blocks-computed) where the schema defines structural configuration sections of data, typically with nested attributes or further blocks.


## Schema Structs
Expand Down