-
Notifications
You must be signed in to change notification settings - Fork 145
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
Migrate monitoring code to V3 API #249
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great! If you want, you can write minitest tests in the test
directory. You can also wait until the new version to do that.
Could you update the Readme in this PR to mention the monitoring version and the date?
@icco done! I think I'll hold off on tests for this one and add them in my new branch PR |
README.md
Outdated
@@ -34,7 +34,7 @@ Fog implements [v1](https://cloud.google.com/dns/api/v1/) of the Google Cloud DN | |||
|
|||
## Monitoring | |||
|
|||
Fog implements [v2beta2](https://cloud.google.com/monitoring/v2beta2/) of the Google Cloud Monitoring API. As of 2016-03-15, we believe Fog for Google Cloud Monitoring is feature complete. We are always looking for people to improve our code and test coverage, so please [file issues](https://github.com/fog/fog-google/issues) for any anomalies you see or features you would like. | |||
Fog implements [v3](https://cloud.google.com/monitoring/api/ref_v3/rest/) of the Google Cloud Monitoring API. We are always looking for people to improve our code and test coverage, so please [file issues](https://github.com/fog/fog-google/issues) for any anomalies you see or features you would like. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you put in today's date with some statement on API coverage?
Thanks! |
Migrate monitoring code to V3 API
After talking about this with @selmanj, we decided to just migrate the models as well and we'll work with partners to migrate them over. One of the resources just doesn't really exist anymore, so we can't really keep it backwards compatible.
Please let me know if everything looks ok! I ended up removing the shindo tests but let me know if you want me to add other tests to compensate - kinda feels dirty without tests.