Skip to content
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

Disable auth validation on harmony client #55

Open
frankinspace opened this issue Feb 12, 2025 · 0 comments · Fixed by #56
Open

Disable auth validation on harmony client #55

frankinspace opened this issue Feb 12, 2025 · 0 comments · Fixed by #56
Assignees
Labels
enhancement New feature or request

Comments

@frankinspace
Copy link
Member

By default the Harmony client will validate EDL credentials when the Client object is initialized. Because bignbit creates many Harmony clients, this can lead to a lot of unnecessary network traffic and load placed on EDL endpoints.

There is an option to disable credential validation when initializing a harmony client, should_validate_auth can be set to False.

Additionally the Harmony client could be made a global variable to that lambda is able to cache the object and re-use it for multiple executions of the lambdas that interact with the harmony API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant