resource_cluster.tags is configurable and passed to CreateCluster, but the actual remote state is ignored because Redpanda will automatically add redpanda-managed: true to the tags.
(This field should also probably be renamed cloud_provider_tags to match the API.)
Solution
An ideal solution lets users configure tags on creation, and then later modify tags and have either (1) the cluster complain that it needs to be recreated or (2) update to include the new tags (when supported by the Redpanda API). The current state is unideal as users can change the configured value and nothing will happen.
Couple ideas, none particularly stand out as the obvious direction to go:
Modify generateModel to ignore redpanda-managed: true from the server if it's not in the plan value
Require users to have redpanda-managed: true in their tags value configured, and default to {redpanda-managed: true} if not configured
Modify the Cloud API to not return redpanda-managed: true if not specified by the user in CreateCluster
Problem
resource_cluster.tagsis configurable and passed to CreateCluster, but the actual remote state is ignored because Redpanda will automatically addredpanda-managed: trueto the tags.(This field should also probably be renamed
cloud_provider_tagsto match the API.)Solution
An ideal solution lets users configure tags on creation, and then later modify tags and have either (1) the cluster complain that it needs to be recreated or (2) update to include the new tags (when supported by the Redpanda API). The current state is unideal as users can change the configured value and nothing will happen.
Couple ideas, none particularly stand out as the obvious direction to go:
generateModelto ignoreredpanda-managed: truefrom the server if it's not in the plan valueredpanda-managed: truein theirtagsvalue configured, and default to{redpanda-managed: true}if not configuredredpanda-managed: trueif not specified by the user in CreateCluster