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

fix(startup): provisioning only in specific auth types #2022

Conversation

talboren
Copy link
Member

No description provided.

Copy link

vercel bot commented Sep 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
keep ⬜️ Ignored (Inspect) Visit Preview Sep 29, 2024 0:24am

@talboren talboren force-pushed the 2021-‍-internal-provisioning-should-only-happen-in-single-tenant-mode branch from 9ee9421 to 4134840 Compare September 29, 2024 12:24
@talboren talboren enabled auto-merge (squash) September 29, 2024 12:26
Copy link
Member

@shahargl shahargl left a comment

Choose a reason for hiding this comment

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

lgtm

@talboren talboren merged commit ab4b44a into main Sep 29, 2024
11 of 13 checks passed
@talboren talboren deleted the 2021-‍-internal-provisioning-should-only-happen-in-single-tenant-mode branch September 29, 2024 12:30
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.

[👨🏻‍💻 Internal]: Provisioning should only happen in single-tenant mode
2 participants