-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[db] Enable spicedb in preview envs #16006
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
Conversation
started the job as gitpod-build-mp-spicedb-preview.1 because the annotations in the pull request description changed |
cff1aea
to
a288495
Compare
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-mp-spicedb-preview.5 |
ab51f2e
to
c4cac34
Compare
c4cac34
to
6688c6a
Compare
31ffb04
to
cf99596
Compare
return nil, nil | ||
} | ||
|
||
if cfg.DisableMigrations { |
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.
out of curiosity: in which cases would you want to disable migrations?
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.
We do this for the CloudSQL in SaaS case where we manage the migrations (across regions) ourselves. Mostly wanted to have the option in case we need it
Description
Configures and deploys spice db in preview envs
Related Issue(s)
Fixes #15951
How to test
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all-ci
Run Leeway with
--dont-test
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh