This repository has been archived by the owner on Feb 11, 2022. It is now read-only.
Add note about unsupported repo #570
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sadly, this is even made more glaring as the Vagrant Plugin development documentation uses this repo as an example for others to follow. Ref: https://www.vagrantup.com/docs/plugins/packaging :( |
|
+1 to this PR. And yes, I'm putting my hand up for it if @mitchellh is interested :) |
gdubicki
added a commit
to gdubicki/vagrant
that referenced
this pull request
Dec 26, 2021
as vagrant-aws had no releases for >5 years and seems to be completely unmaintained as of now (see mitchellh/vagrant-aws#570)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey there @mitchellh - We were hoping that we could get a note on this repo to let people know that this plugin is no longer supported. I think maybe @rtyler is a maintainer too? Either way, it doesn't look like there's been much traction on any of the issues or pull requests, so it would be nice to let folks know that this plugin isn't really being supported. There has been some confusion around if this is something official (since it's on @mitchellh 's page) and supported, since there are other HashiCorp tools where this is true.
The other alternative is the archive this repo so it's clear that support has stopped. That would prevent others from contributing fixes or opening issues, but it doesn't look like those are being triaged anyway. At the very least, this pull request adds a note to the README and new issue templates to let folks know what's going on.
Hope that makes some sense! Let me know if there's anything I can do, thanks!