v2.5.0-alpha

What's Changed

This release addresses missing permissions in the managed-cloud sub-module used for establishing StreamNative's vendor access.

In addition to these needed changes, we have also updated the tiered-storage-resources sub-module to align better to the permissions defined in the managed-cloud sub-module.

Breaking Changes

• Those who have deployed the managed-cloud sub-module while using the runtime_hosted_zone_allowed_ids input will have found that the hosted zone ARN was needed and not its ID. This has now been updated in v2.5.0-alpha, and will correctly accept the hosted zone ID instead of the ARN.
• The input runtime_s3_bucket_pattern in the tiered-storage-resources sub-module has been renamed to s3_bucket_pattern, as it is used for both runtime and standard modes.
• The naming convention for the offload S3 bucket has changed to better align with StreamNative's vendor access IAM policies. If you have previously used the tiered-storage-resources submodule, the input bucket_name_override will allow you to specify the current name of your S3 bucket. This will prevent Terraform from wanting to destroy/recreate the S3 bucket.
• The input create_iam_policy_for_tiered_storage in the tiered-storage-resources sub-module has been renamed to use_runtime_policy.
• The input iam_policy_arn in the tiered-storage-resources sub-module has been removed.
• The default value of service_account_name in the tiered-storage-resources sub-module has changed from pulsar to pulsar-broker, which is the default KSA created for the Pulsar Broker component in StreamNative Cloud deployments.

Full Changelog: v2.4.2-alpha...v2.5.0-alpha