et304383

@apparentlymart thanks. I think option one is best. 3 doesn't work as we create the VPC with terraform in the same workspace.

Everyone commenting with "+1" should know that GitHub has a +1 reaction you can give to the original request which goes much further in terms of prioritizing an item as...

@lourdesmm90 @deblinaalways @shishiranshuman13 is this a joke? You're literally commenting with a +1 after a post about why +1 comments are useless and just create unnecessary emails to those watching...

Anyway, back to the issue. https://github.com/aws/amazon-cognito-identity-js/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc @itrestian this is the most +1'd feature in your issue list yet it's been over a year with no enhancement. Why is this not...

Apreciate all the work that goes into the serverless framework but this REALLY needs to be top priority. AWS is driving everyone to use IAM Identity Center now and relying...

> Sincere apologies for the slow action here. This has been completed in upcoming V.4. So does this mean it won't be in place until the next major serverless release...

> @et304383 Yes. To fix this, we had to rework the traditional credential handling that the Framework has had for many years, so it is a breaking change, fitting the...

I don't understand why the `aws sso login` command can't just take a session duration parameter like sts assume role does. This is unfortunate and confusing behaviour.

This is a serious deficiency in the docs. I wasted hours trying to figure out why this error was only thrown when using a conditional filter inside the for_each. @jbardin...

If anyone comes across this thread from Google and is shocked that Hashicorp still hasn't provided a quiet output flag, this gist will help if you are willing to apply...