Terraform-provider-aws: What can be done to move the AWS Amplify service forward?

Resources for the AWS Amplify service have been stuck in review for 8+ months and I’m wondering how we can move that forward. I have been using these resources for 6+ months in production and I’d love to get off of the custom fork required to use them. Is the only solution :+1:'s?

Here is the issue / PRs in question from @k24d (who did almost flawless work from what I can tell in my usage):

  1. https://github.com/terraform-providers/terraform-provider-aws/issues/6917
  2. https://github.com/terraform-providers/terraform-provider-aws/pull/11928
  3. https://github.com/terraform-providers/terraform-provider-aws/pull/11936
  4. https://github.com/terraform-providers/terraform-provider-aws/pull/11937
  5. https://github.com/terraform-providers/terraform-provider-aws/pull/11938
  6. https://github.com/terraform-providers/terraform-provider-aws/pull/11939
2 Likes

+1 from me, I’d love to be able to manage these resources through Terraform!

1 Like

The original dev for this work has just today replied back that his PRs are out of date and he doesn’t have time at the moment to follow up on those PRs to bring them up-to-date. So unfortunately, it looks like this has stalled long enough that it needs someone new to take it over.

Any takers? :smile:

If no one picks it up by December or January then I can try to take it over as I’ll have more free time starting then.

For anyone following, @ ashishmohite has put up an updated PR @ #15966 which addresses the issues from the original comment.

Any suggestions on moving this forward is much appreciated!