-
Notifications
You must be signed in to change notification settings - Fork 1
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
Allow not using signed URLs on consumers #9
Conversation
} | ||
} | ||
|
||
if creds.JSON != nil && !externalAccount { |
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.
what if it is an external account?
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.
With an external_account we now fall into the else portion which the client is prepared to work with a number of formats including external_account. It was a case that when finding the default credentials for external_account format they still filled in creds.JSON which we did not really need and made us fall into the signed url code.
Sometimes the broker sends a signed URL to a consumer to allow them to retrieve fragments directly from buckets. Some of our customers do not like adding the required permissions to allow the broker to be able to sign. We had an earlier PR that was merged into the arize branch which allowed us to turn off signing on the broker side. This PR is required for the consumers to properly work with the earlier broker change to avoid using signed URLs.