Closed mbbush closed 8 months ago
@mbbush thanks for reporting this, I've sent a PR for this, which I've locally validated the endpoint configuration is properly propagated. If possible, would you be willing to test with https://github.com/upbound/provider-aws/pull/1066 check if the fix works for you too?
Thanks for the quick fix! Yes, when I build and deploy #1066 it resolves the issue for me.
@mbbush many thanks for testing it, and glad that it is working 🎉 Could you also check that #1066 still works for CLI-based resources too in your localstack setup?
CLI-based resources work too. One of the resources I'm currently working with is UserPoolClient.cognitoidp, and that works fine with the build from #1066
What happened?
Using provider version v0.45.0 I can successfully test my compositions and managed resources against localstack, which locally simulates the aws api. Starting with provider version v0.46.0, I cannot. The error is also present in v0.47.1, and when I run against the current tip of
main
. When I revert 7a61c51f89e7a38c640250b68583765f030b6bda it works again.All resources which use the no-fork reconciler get a Synced: False condition
The resources which still use the CLI based reconciler work fine.
Provider logs:
How can we reproduce it?
Install localstack
Set up the following providerconfig:
Run uptest on examples/iam/role.yaml (or anything else)
What environment did it happen in?