Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how should we impliment vpcs #75

Closed
ghost opened this issue Apr 29, 2020 · 4 comments
Closed

how should we impliment vpcs #75

ghost opened this issue Apr 29, 2020 · 4 comments

Comments

@ghost
Copy link

ghost commented Apr 29, 2020

For those of you planning on making use of vpcs in your tests, how do you want it to work in kitchen-digitalocean? Looking for feedback before implementing it.

@ghost ghost added the Feedback Wanted label Apr 29, 2020
@ghost ghost self-assigned this Apr 29, 2020
@zetas
Copy link

zetas commented May 1, 2020

I was actually just trying to update my cookbooks to use the new VPC feature because I want to test that some of my VPC based services are available from the nodes spun up by chef. I'd like it to work just like the VPC id selector in the AWS module, effectively: vpc_id: my-vpc-id in the yaml would be just fine. I don't think it's necessary to handle creating VPC's and stuff from test kitchen but that's just my 2cp.

@ghost
Copy link
Author

ghost commented May 5, 2020

I'll do this and cut a release sometime this week. Been super busy sorry.

@zetas
Copy link

zetas commented May 5, 2020

No need to apologize friend. You do great work, thanks for maintaining this amazing repo!

@ghost ghost closed this as completed in d0ab71b May 18, 2020
@ghost
Copy link
Author

ghost commented May 18, 2020

This is ready to rock in 0.11.0. Please open a issue if there are any issues.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant