Skip to content
This repository has been archived by the owner on Feb 11, 2022. It is now read-only.

Project Vargant and Vagrant-AWS plugin are dead #543

Open
planesweep opened this issue Jun 6, 2018 · 4 comments
Open

Project Vargant and Vagrant-AWS plugin are dead #543

planesweep opened this issue Jun 6, 2018 · 4 comments

Comments

@planesweep
Copy link

planesweep commented Jun 6, 2018

Hi,
in my opinion the project vagrant-aws plugin is dead. Currently there are 233 issues and 25 open pull requests.

Is there someone who feels responsible for the code?

@ghost
Copy link

ghost commented Jun 14, 2018

+1

@SpoddyCoder
Copy link

Well Vagrant isn't dead by any stretch... but yes, this project looks like it's sunsetting :(

It does still work, just! If you have an existing project, upgrade to all the latest tooling (vagrant + plugins, chef, parallels) and apply the fixes detailed in this issue thread...

#365

But certainly not recommended for any new projects.

It is a shame because the AWS built-in solution, OpsWorks, works out ~$15p/month for a single instance. When a micro-instance capable of running a dozen low traffic websites can cost as little as $6-7 p/month - the OpsWorks management cost kills the economics. This plugin fitted very neatly for those simple, ultra low cost use cases.

@naviat
Copy link

naviat commented Nov 15, 2018

+1
I moved to use terraform.

@ghost
Copy link

ghost commented Aug 10, 2019

@planesweep I believe you just nominated yourself

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants