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

[chore] Migration cleanup #192

Merged
merged 4 commits into from
Mar 31, 2024
Merged

[chore] Migration cleanup #192

merged 4 commits into from
Mar 31, 2024

Conversation

nwithan8
Copy link
Owner

  • Final migration from V1 config to V2 config. Confirmed working in following scenarios:

    • User has a config.yaml file and has already run M1 -> (M1 runs again), M2 runs (ignores M1 output)
    • User has a config.yaml file and has not already run M1 -> M1 runs, M2 runs (ignores M1 output)
    • User has environmental variables and has already run M1 -> (M1 runs again), M2 runs
    • User has environmental variables and has not already run M1 -> (M1 runs again), M2 runs
    • User has a new tauticord.yaml file -> No migrations run
  • Improve YAML schema with input restriction

- Improve, remove dependencies for 001_env_var migration
- Account for M1-file migration in M2
- Update Dockerfile to look for new tauticord.yaml config file
@nwithan8 nwithan8 merged commit a0ab91a into master Mar 31, 2024
1 check passed
@nwithan8 nwithan8 deleted the migration_cleanup branch March 31, 2024 01:47
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.

1 participant