-
Notifications
You must be signed in to change notification settings - Fork 0
15 tom eso api client library enhancements #23
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
base: dev
Are you sure you want to change the base?
Conversation
Bumps [flake8](https://github.com/pycqa/flake8) from 7.0.0 to 7.3.0. - [Commits](PyCQA/flake8@7.0.0...7.3.0) --- updated-dependencies: - dependency-name: flake8 dependency-version: 7.3.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bump flake8 from 7.0.0 to 7.3.0
Bumps [tomtoolkit](https://github.com/TOMToolkit/tom_base) from 2.25.0 to 2.25.1. - [Release notes](https://github.com/TOMToolkit/tom_base/releases) - [Commits](TOMToolkit/tom_base@2.25.0...2.25.1) --- updated-dependencies: - dependency-name: tomtoolkit dependency-version: 2.25.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
…abot/pip/tomtoolkit-2.25.1
Bump tomtoolkit from 2.25.0 to 2.25.1
Also, get the ESO P2 credentials from the ESOProfile.
The installation has been simplified by using the integration points and the ESOProfile to store credentials.
jchate6
left a comment
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.
I would also add an explanation for the default username/profile situation to the profile card itself. Make the explanation conditional on if the default is currently set, so users with actual credentials don't see it.
jchate6
left a comment
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 PR refactors the ESO facility integration to use user-specific credentials from the
ESOProfile.ESOProfileESOAPIclass is refactored to require explicitenvironment,username, andpasswordparameters, removing the singleton pattern and settings dependency.NotImplementedErrorfor clarity.Also, merged into this branch:
The facility is still in prototype stage and we may even want to rethink the ESO P2 Tool iframe in lieu of opening up the ESO P2 Tool in another browser TAB/window, but we should get some customer feedback @talister and @carrholt first and foremost.