-
Notifications
You must be signed in to change notification settings - Fork 112
fix: report change in check mode when schema exists and state is absent #858
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
|
PS: could use some help (if the change is correct) with the tests... |
|
There's an assert somewhere in the code, which is failing: |
hunleyd
left a comment
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.
needs a changelog fragment before merging
|
@allartk thanks for submitting the fix
|
|
Thanks for the feedback, I'll try to fix, as soon as my schedule allows it. |
* AZP: add RHEL 10.0 to devel remote target * Update README * fix tests * fix copy-paste thing
|
@allartk thanks for the fix! |
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #861 🤖 @patchback |
…nt (#858) (#861) * fix: report change in check mode when schema exists and state is absent * AZP: add RHEL 10.0 to devel remote target (#859) * AZP: add RHEL 10.0 to devel remote target * Update README --------- (cherry picked from commit 8b2d17b) Co-authored-by: allartk <allartk@gmail.com> Co-authored-by: Andrew Klychkov <aklychko@redhat.com>
SUMMARY
Removing an existing schema in check mode does not report changes.
However, removing a non-existing schema in check mode does.
ISSUE TYPE
COMPONENT NAME
postgresql_schema
ADDITIONAL INFORMATION
Example