Flávio Moringa

I'm having the exact same same issue and I'm a stuck... createing the TGW peering accross accounts seems impossible right now using terraform because I cannot get the correct attach...

@haarchri I can try yes. Anything there you feel might help? We already upgraded from 1.7 to 1.8 hoping for improvements, but nothing changed. But we will try with 1.9.

@haarchri We are still with the issue of upgrading to 0.32.0 without the provider revision being healthy... Do you think we can upgrade to 1.9.1 like this, or the aws-provider...

I upgraded crossplane to 1.9.1 as @haarchri mentioned above, and after that I Upgraded aws-provider from v0.31.0 to v0.32.0. Maybe it takes more time, but It's been 20 minutes and...

What I also see is that when I do "k describe providerrevisions crossplane-provider-aws", both old and new versions shows up (0.31.0 and 0.32.0)... I remember this happening before, and I...

New version: ``` $> k describe providerrevisions crossplane-provider-aws-245ce7fb587d Name: crossplane-provider-aws-245ce7fb587d Namespace: Labels: pkg.crossplane.io/package=crossplane-provider-aws Annotations: meta.crossplane.io/description: The Amazon Web Services (AWS) Crossplane provider adds support for managing AWS resources in Kubernetes....

But.. just checked and in one of our clusters where we upgraded from 0.29.0 to 0.32.0 It seems we also have both versions still there, but we have this: ```...

seems ok: ``` $> k describe pod crossplane-provider-aws-245ce7fb587d-bf996f7bb-pcvhh -n caas-base | grep Image Image: crossplane/provider-aws:v0.32.0 Image ID: docker.io/crossplane/provider-aws@sha256:245ce7fb587dd634dbf92b584aa24b1ef58bc1a1fdee023132028e9535efad0b ``` Regarding health, it seems after 4 or 5 hours the new...

I'm also waiting for this for a while. I see it being worked on here: https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/1109 but not moving forward. This is actually a big pain point for us right...

@bryantbiggs @AlexisColes Is there something that can be done to unblock the merge? The current issue with the computed values as keys in maps could maybe be fixed in another...