While this PR aimed to only add automation to refreeze etc, I found that it fails unless updating google-cloud-logging as pip-compile concluded we had incompatible versions otherwise.
The code that could risk breaking when updating google-cloud-logging resides in mybinder.org-deploy rather than in this repo. But, I don't think it will break based on reading the migration guide.
This may have influenced the logs emitted, but maybe not? =/ Unsure.
With 3.0.0, when a log doesn't specify a monitored resource, the library attempts to identify the resource. If a resource can't be detected, the field will still default to "global".
While this PR aimed to only add automation to refreeze etc, I found that it fails unless updating
google-cloud-logging
aspip-compile
concluded we had incompatible versions otherwise.The code that could risk breaking when updating google-cloud-logging resides in mybinder.org-deploy rather than in this repo. But, I don't think it will break based on reading the migration guide.
This may have influenced the logs emitted, but maybe not? =/ Unsure.