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

Add Origin Information to Namespace Endpoint (SOFTWARE-5629) #3293

Merged
merged 2 commits into from
Jul 27, 2023

Conversation

CannonLock
Copy link
Collaborator

@CannonLock CannonLock force-pushed the add-origin branch 2 times, most recently from 4751f99 to 3ccf9d6 Compare July 25, 2023 19:01
@CannonLock
Copy link
Collaborator Author

CannonLock commented Jul 25, 2023

Tested by sorting the results, then comparing the current and the new response to make sure the only thing changed was the addition of the origin information.

Resulting json files are zipped below.

Archive.zip

@CannonLock
Copy link
Collaborator Author

Final changes. With a diff of the previous and the new result of this endpoint I can confirm this PR changes none of the current information, only adding origin lists to each namespace.

Archive 2.zip

Copy link
Collaborator

@matyasselmeci matyasselmeci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typing.Literal was added in Python 3.8; scripts in bin/ such as osg-scitokens-config might get run with Python 3.6 so we can't use any features from newer versions yet.

@CannonLock
Copy link
Collaborator Author

@matyasselmeci Ah, I remembered we got the webapp to 3.9 but makes sense others run this.

@CannonLock CannonLock force-pushed the add-origin branch 3 times, most recently from 3e10747 to 6f1eb73 Compare July 26, 2023 19:58
@CannonLock
Copy link
Collaborator Author

Sorry for the force pushes I misspelled "remot(v)e" and then proceeded to forget how to rebase.

Copy link
Collaborator

@matyasselmeci matyasselmeci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@matyasselmeci
Copy link
Collaborator

No worries, LGTM. Can you merge or rebase on master?

@matyasselmeci
Copy link
Collaborator

Once it's up to date, feel free to merge and deploy.

@CannonLock CannonLock merged commit 422150f into opensciencegrid:master Jul 27, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants