Can I borrow the demo.key for other open source project based on gcloud-python?

[littleq0903]

As title, I am making a Django storage backend based on Google Cloud Storage, and in build testing it will need a bucket for testing, I found one demo.key under gcloud.storage, can I borrow the key, client_email, and bucket for the testing purpose too? (like on Travis)

https://github.com/littleq0903/django-gcloud-storage

[dhermes]

@littleq0903 Please do not do this. We are trying to do something else. I can CC you on that eventual PR to give you an idea of what to do.

[littleq0903]

OK, got it.

Thank you, currently I didn't commit the secret part onto github yet.

Or have testbed-like mocking mechanism in this project?
On Nov 23, 2014 1:59 AM, "Danny Hermes" [email protected] wrote:

@littleq0903 https://github.com/littleq0903 Please do not do this. We
are trying to do something else. I can CC you on that eventual PR to give
you an idea of what to do.

—
Reply to this email directly or view it on GitHub
#381 (comment)
.

[silvolu]

Thanks for asking! Any reasons why you couldn't create and use your own key to test the project?

[tseaver]

#383 removes the key (and other credentials info) from the tree, and updates the docs for the demos to describe how to add the required keys to the environment to replace them.

[littleq0903]

I've created my own key and credentials for Travis CI already.

https://github.com/littleq0903/django-gcloud-storage

Just curious about whether the key in the demo folder is for testing purpose, to avoid some cost by unittest.

Sorry for asking this :)

[tseaver]

FWIW, the original reason for having the keys / credentials checked in was to allow somebody to install the library and run the demos for evaluation without needing to configure their own:

$ /path/to/venv/bin/pip install gcloud
$ /path/to/venv/bin/python -m gcloud.datastore.demo
$ /path/to/venv/bin/python -m gcloud.storage.demo

[littleq0903]

yeah, I noticed this :D