Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
warehouse: add initial pending OIDC provider models #12572
warehouse: add initial pending OIDC provider models #12572
Changes from 3 commits
6261b76
66b5631
d18dbbc
1756410
ef67edd
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Flagging for review: I had to dupe this
UniqueConstraint
betweenGitHubProvider
andPendingGitHubProvider
, even though they're functionally equivalent, thanks to the uniquename
requirement. There might be a better way to do this, though.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 think this is due to not having set any naming_conventions for this project in the global metadata setup
warehouse/warehouse/db.py
Line 77 in d58e6b2
Alembic docs go into it here: https://alembic.sqlalchemy.org/en/latest/naming.html
I think we always named them manually, like here:
warehouse/warehouse/accounts/models.py
Line 197 in d58e6b2
So it might be a future refactoring to replace the manually-named constraints, but I’d approach that with some serious caution 😉