v2.1.6

What's Changed

• fix vc and sr provider descriptions to include azure by @rmb938 in #163

Full Changelog: 2.1.6...v2.1.6

Add more detail to workspaces and user roles documentation strings

Specify that the workspaces and user roles features aren't available to all WarpStream customers by default.

v2.1.5

Extend user roles resource to support in-place updates.

v2.1.4

Merge pull request #160 from warpstreamlabs/topicconfigset

topic configuration is unordered so it needs to be a set

v2.1.3

Schema Registry Agent Key (#158)

v2.1.2

• Add a new enable_deletion_protection field in the warpstream_topic resource. If this is set, it will be impossible to delete the topic, either from Kafka clients, or from the UI, or from terraform. The flag must be set to false before the topic can be deleted.

v2.1.1

Extend the workspace resource to support renaming an existing workspace.

v2.1.0

Previously, creating a virtual cluster or schema registry using the WarpStream Terraform provider would automatically create an agent key assigned to the new virtual cluster or schema registry resource. This side effect is now removed.

v2.0.3

When provisioning a new workspace, do not create a new application key for that workspace unless specified by the Terraform run.

v2.0.2

• Add warpstream_user_role resource and data source.
• Allow provider token to be passed dynamically so that account keys and application keys can be managed in a single Terraform state.