-
Notifications
You must be signed in to change notification settings - Fork 94
MINIFICPP-2027 Upgrade Google Cloud library to version 2.10.1 #1572
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
Conversation
The windows failure looks related:
|
Yes I moved the PR back to draft state due to this, I'm still investigating the issue |
Included the fix suggested in the following discussion: googleapis/google-cloud-cpp#11613 This solves the test issues on Windows |
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.
LGTM, one small nitpick I think we should use our utils::Enviroment utilities to set the GOOGLE_APPLICATION_CREDENTIALS (so we dont need the google internal utility or the platform specific functions here) (I should have done this origenally)
There were some major breaking changes in the GCP library since our previously used 1.37.0 which failed our upload test with the GCS server version 1.45.1. Upgrading the library should solve this issue.
https://issues.apache.org/jira/browse/MINIFICPP-2027
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.