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

feat(db): add ability to change schema name #2126

Merged
merged 11 commits into from May 13, 2024
Merged

Conversation

bodinsamuel
Copy link
Contributor

Describe your changes

Contributes NAN-900

  • Allow to change the default schema name
    For testing purpose, local dev, and also to be able to have multiple install in the same DB. @khaliqgant I believe it could also match your local setup.
    I need this to be able to run some specific integration tests

@bodinsamuel bodinsamuel self-assigned this May 9, 2024
@TBonnin
Copy link
Collaborator

TBonnin commented May 9, 2024

Does this only apply to the main db or should we do the same for records as well?

@bodinsamuel
Copy link
Contributor Author

Good question, I did it while debugging the main db but could be interesting to have it for all db. Let me change that

@bodinsamuel
Copy link
Contributor Author

Can I have a review on this please? ☺️ @TBonnin @khaliqgant

@bodinsamuel bodinsamuel enabled auto-merge (squash) May 13, 2024 12:55
## Describe your changes

- Test `encryptDatabaseIfNeeded` 
Only check environment because that what I was trying to fix

## How to test?

- Removing `NANGO_ENCRYPTION_KEY` from your .env should throw `Error: A
previously set NANGO_ENCRYPTION_KEY has been removed from your
environment variables.`
- Changing `NANGO_ENCRYPTION_KEY` should throw `Rotation of
NANGO_ENCRYPTION_KEY is not supported.`
@bodinsamuel bodinsamuel merged commit 9b26a79 into master May 13, 2024
18 checks passed
@bodinsamuel bodinsamuel deleted the fix/schema-migration branch May 13, 2024 16:12
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.

None yet

2 participants