SPOC-307: Block zodan if lolor is installed on new node #245
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The pgEdge lolor extension creates tables in the lolor namespace schema to contain user large object data.
If lolor is installed on the target node when zodan is run, users currently get a message about there being existing user tables, and it fails (no user tables existing is a requirement of zodan).
It can be confusing for users to understand what the issue is. To make it clearer to zodan users, add an explicit check to tell the users that they should not have lolor installed on the target node.