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
It is worth to be fixed for queues. But it might not be accurate for buckets. As their names are used as globally unique identifiers, it is more obvious to define them explicitly. Also, another case related to bucket names: if a bucket is used to store a static site, the bucket name should match the site's domain name. So implicit changes could break the rule. If you need to define bucket names based on the project name, you should use the variable interpolation serverless framework provides. E.g.
When using AWS SQS client the queue created lacks the project prefix. Might be the case for all AWS compatible resources that use non-yc SDK
The text was updated successfully, but these errors were encountered: