search

crossplane-contrib / provider-upjet-aws

Official AWS Provider for Crossplane by Upbound.
https://marketplace.upbound.io/providers/upbound/provider-aws
Apache License 2.0
143 stars 120 forks source link

Remove provider-aws-opsworks once its EOL is complete in May 2024 #1224

Closed mbbush closed 1 month ago

mbbush commented 6 months ago

AWS Opsworks is closed to new customers, and scheduled to become unavailable to all existing customers in the next few months. This means we can remove it from provider-aws, to slightly reduce the size, maintenance, and testing burdens of the provider.

We should wait until AWS has actually completed their shutdown, as they have extended these types of EOL dates in the past.

Currently, the shutdown schedule is March 31, 2024 for Puppet, May 5, 2024 for Chef, and May 26, 2024 for stacks.

I've never used this service myself, so I don't actually know which managed resources are used for puppet vs chef vs stacks. I'm inclined to wait until all three are shut down, then remove the provider entirely.

Note that we can also remove the opsworks exception from the RegionAddition override.

Given that the service will no longer exist, although technically its removal would be a breaking change, I'm inclined to release the removal in a normal minor version bump. If there are good reasons not to do so (or reasons to not remove them at all), I'd be happy to hear them.

These resources were originally added in PR #444 (issue #313) . I'm curious if anyone involved in adding them knows if they were specifically requested, or merely added as part of systematically going through all the terraform-provider-aws resources to get broad crossplane support.

jeanduplessis commented 6 months ago

@mbbush these were added as part of our expansion of resources effort. I'm not aware of anyone specifically asking for them.

I would not be against us removing the resources.

I think doing this as part of a minor release is acceptable since the service no longer exists.

github-actions[bot] commented 1 month ago

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. 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.

github-actions[bot] commented 1 month ago

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!