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

Dry run for nodecloud gcp plugin #3

Open
raju249 opened this issue Sep 15, 2018 · 1 comment
Open

Dry run for nodecloud gcp plugin #3

raju249 opened this issue Sep 15, 2018 · 1 comment

Comments

@raju249
Copy link
Contributor

raju249 commented Sep 15, 2018

After the new architecture is implemented, we have to check for the working of nodecloud gcp plugin whether or not it works as expected. Any bugs encountered, we will have to fix that.

@jmularski
Copy link
Contributor

Tested it out with example tests in nodecloud. Google object storage seems to work for me, was not able to test google-dns since I don't have free domain to test on (don't want to experience on my prod domains). Google compute outputed completely nothing, and I have one compute instance already created. After I created datastore instance, it works great, and it seems easy to use. I still think you should enter some README.md with developer workflow (referring to issue #2 ), and switch from massive google-cloud depreciated library, to @google-cloud/xxxxx (fe @google-cloud/storage) libraries, that have ongoing support.

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

No branches or pull requests

2 participants