Disable auto code generator for postgres migrations#3820
Conversation
|
Skipping CI for Draft Pull Request. |
md2119
left a comment
There was a problem hiding this comment.
Can we add a check in the generator code to errors out if a migration flag is encountered? It will ensure that nobody mistakenly adds a migration.
|
Images are ready for the commit at 0e6b70d. To use with deploy scripts, first |
|
Do we need to update the comment in the generated files or is that OK to leave? Or do we just deal with that if we need to update something in one of those files? |
|
Let's leave it as is. Most likely and ideally we don't need to update them anymore. They would be obsoleted in a few releases. |
|
Description
Disable auto code generator for postgres migrations.
This one will be after the schema freeze PR and for 3.74 #3769
Checklist
[ ] Unit test and regression tests added[ ] Evaluated and added CHANGELOG entry if required[ ] Documented user facing changes (create PR based on [openshift/openshift-docs](https://github.com/openshift/openshift-docs) and merge into rhacs-docs)~If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.