Project status

[dudicoco]

How does the release of the new upbound aws provider affect this project?

The official docs now direct users to use the ubound provider, which means there will be less and less usage of this provider over time.
It is confusing for users to understand why there are two different aws providers (personally I had to dig in to figure this out) and which one they should choose.

What does the future hold for this project? Is there a reason for it to live side by side with the upbound provider instead of joining forces on a single provider?

[jonashackt]

This announcement post https://blog.crossplane.io/charter-expansion-upjet-donation/ states valualbe insights:

"Upbound has donated to the Crossplane project their entire Upjet provider framework as well as key Crossplane providers for the major cloud providers."

Later in the article the current confusion is also described - and in the paragraph Opportunity for convergence the strategy to tackle it is described as an open process:

"The ecosystem of Crossplane providers has some fragmentation and in some cases there are multiple provider options for a single targeted offering, e.g., AWS. This has caused confusion amongst the community about the differences between the providers, which provider to use, etc. Now that providers are part of the project, we can work as a community to converge upon single provider implementations that we can all rally around. Any effort to converge would be an open discussion in a collaborative fashion amongst the community."

And later

"Converging upon a set of endorsed providers for the project will greatly reduce confusion about which providers to use, but we won’t get to that destination without involvement and collaboration from the entire community."

So I guess this topic is an ongoing process in the crossplane ecosystem right now.

[MisterMX]

A short statement to clarifiy the status and future of this repository:

Upbound has moved to its own Terraform-based set of providers. This means that https://github.com/crossplane-contrib/provider-aws is now only maintained by community volunteers since there is a number of people out there who are still using it.

It is kind of legacy but it will receive further updates as long as the community is willing to contribute to it. Due to the limited number of active maintainers - two at the time of writing - there is no capacity to implement new controllers. So all issues labeled as enhancement will most likely not be treated by us. However, we do accept PRs for new features or bug fixes.

Since the core resources (IAM, RDS, S3 etc.) are pretty much matured it should be safe to continue with this provider should your Crossplane platform already run with it. For new projects we recommend to use https://github.com/upbound/provider-aws as we project a better long-term support for it.

I hope that cleared things up a bit.

BTW: If someone is willing to become a maintainer for this repository, feel free to send me a PM on Crossplane Slack.

[dudicoco]

Thanks for the info @MisterMX.

I believe it would be beneficial to include this information in the repo's readme.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.