Cluster fail to deploy - when having more tags or whitespace in tags

[archith-kadannapalli]

ROSA HCP clusters fail to deploy when using RH provided terraform module when

1. Using more tags (can be reproduced adding 18-19 tags)

2. Any white space is present in tags

Steps for reproducing and results :

1. Using the ROSA HCP terraform module from github repo deploy a cluster with adding either 17+ tags (passed through variables.tf and called in main.tf) or any tag with a white space or both.

   1a .If more than 17 tags are present the cluster fails to deploy with error log (says invalid subnet) similar to the below in cloudtrail

"errorCode": "Client.InvalidSubnetId.Malformed",
    "errorMessage": "Invalid Subnet Id: '' (expecting 'subnet-...; the Id may only contain lowercase alphanumeric characters and a single dash')",  

1b. When white space is present in any of the tags, the deployment fails with error :

│ Can't create cluster with name '<clustername>': status is 400, identifier is '400', code is 'CLUSTERS-MGMT-400', at '2025-05-12T01:04:19Z' and operation identifier is
│ 'xxxxxxxxxx-xxxx-xxxx-xxxxx-xxxxxxxxx': Given tags can't be used for Hosted Control Plane cluster: 'invalid tag(s) detected: 
│ invalid tag value 'th ree space' at key 'tag3': {expected to match '^[0-9A-Za-z_.:/=+-@]+$'}'     

[archith-kadannapalli]

Adding a comment from @gdbranco from an internal discussion.

_So there are two things here
Whitespace in tags would need to be handled by terraform as if the response from the service or resource is different than input it will complainThe amount of tags is something that we need to ask the hypershift team to include ocm additional tags in the system slice rather than consider it customer. AWS allows for 50 tags in total and that is split 50/50 to use internally and by customer. However ocm tags are going into the customer bucket right now so it fails the installWould that be it for both of these?_