You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the prefix option to deploy multiple watchbot services using a single CFN stack. This works fine for most parameters, but trying to set different values for the cluster results in an error:
Error: Outputs name used more than once: ClusterArn
The ClusterArn appears to be treated differently than the other options in that it isn't prefixed, so defining multiple watchbot services in a single template fails unless the cluster is always the same. Is having multiple clusters within a single stack something that watchbot can support?
The text was updated successfully, but these errors were encountered:
Sure. I can (I think) preserve existing behavior by setting an overall ClusterArn if and only if all clusters are the same. That avoids a breaking change for downstream consumers that may be relying on the current ClusterArn output value while setting prefixes.
Hm, I think that the lack of prefixed output here is a straight-up bug. Yes, it'd be a breaking change, but I think it is better to break the bugged behavior and make a new major version release.
I'm using the
prefix
option to deploy multiple watchbot services using a single CFN stack. This works fine for most parameters, but trying to set different values for thecluster
results in an error:The ClusterArn appears to be treated differently than the other options in that it isn't prefixed, so defining multiple watchbot services in a single template fails unless the cluster is always the same. Is having multiple clusters within a single stack something that watchbot can support?
The text was updated successfully, but these errors were encountered: