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.

Sign up for GitHub

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

Jump to bottom

[drizzle-kit] Change to create the drizzle studio directory on studio command execution instead of on import #3422

Open

oreshinya wants to merge 1 commit into drizzle-team:main from oreshinya:mkdir_only_when_studio

oreshinya commented Nov 5, 2024

Change to create the drizzle studio directory on studio command execution instead of on import.

Background

Regarding application operation in k8s:

For web applications, setting securityContext.readOnlyRootFilesystem to true is a common security recommendation
It's a common workflow to perform database migrations through k8s jobs using the app's docker image during deployment
Despite only needing to call the migrate command, drizzle-kit forcibly creates a drizzle studio directory
Due to this write operation by drizzle-kit, we cannot set securityContext.readOnlyRootFilesystem to true

Currently, we work around this issue by including the directory in the docker image beforehand. However, this workaround is undesirable.


          Make directory when studio is called

bfa1d05

oreshinya changed the base branch from main to beta

November 5, 2024 08:12

oreshinya changed the base branch from beta to main

November 5, 2024 08:14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet