-
Notifications
You must be signed in to change notification settings - Fork 633
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
Add sqlalchemy db.statement sanitization flag #1701
Open
nemoshlag
wants to merge
18
commits into
open-telemetry:main
Choose a base branch
from
nemoshlag:sqlalchemy-query-sanitization
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
be7ac86
add sqlalchemy sanitization flag
nemoshlag 0fe4aad
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag e3ad469
changelog entry
nemoshlag 1c9f944
add no side effects check to tests
nemoshlag 16a5032
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag b7c57b4
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag 031895c
Merge branch 'main' into sqlalchemy-query-sanitization
shalevr f931968
Update CHANGELOG.md
nemoshlag b0e6f6e
fix sanitized default value
nemoshlag 5fb5fd3
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag d11d3b8
spellcheck fix
nemoshlag 4d6d67f
doc fix
nemoshlag b43fc33
add CHANGELOG entry
nemoshlag 892d9b0
Update CHANGELOG.md
nemoshlag f1e481e
fix sql sanitization
nemoshlag 91079f5
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag 262acab
Merge branch 'main' into sqlalchemy-query-sanitization
nemoshlag dfd26b5
Merge branch 'main' into sqlalchemy-query-sanitization
shalevr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43 changes: 43 additions & 0 deletions
43
instrumentation/opentelemetry-instrumentation-sqlalchemy/tests/test_engine.py
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# Copyright The OpenTelemetry Authors | ||
# | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# you may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
from opentelemetry.instrumentation.sqlalchemy.engine import ( | ||
_normalize_vendor, | ||
_sanitize_query, | ||
) | ||
from opentelemetry.test.test_base import TestBase | ||
|
||
|
||
class TestSQLAlchemyEngine(TestBase): | ||
def test_sql_query_sanitization(self): | ||
sanitized = "SELECT ? FROM ? WHERE ? = ?" | ||
select1 = "SELECT * FROM users WHERE name = 'John'" | ||
select2 = "SELECT * FROM users WHERE name = 'John'" | ||
select3 = "SELECT\t*\tFROM\tusers\tWHERE\tname\t=\t'John'" | ||
|
||
self.assertEqual(_sanitize_query(select1), sanitized) | ||
self.assertEqual(_sanitize_query(select2), sanitized) | ||
self.assertEqual(_sanitize_query(select3), sanitized) | ||
self.assertEqual(_sanitize_query(""), "") | ||
self.assertEqual(_sanitize_query(None), "") | ||
|
||
def test_normalize_vendor(self): | ||
self.assertEqual(_normalize_vendor("mysql"), "mysql") | ||
self.assertEqual(_normalize_vendor("sqlite"), "sqlite") | ||
self.assertEqual(_normalize_vendor("sqlite~12345"), "sqlite") | ||
self.assertEqual(_normalize_vendor("postgres"), "postgresql") | ||
self.assertEqual(_normalize_vendor("postgres 12345"), "postgresql") | ||
self.assertEqual(_normalize_vendor("psycopg2"), "postgresql") | ||
self.assertEqual(_normalize_vendor(""), "db") | ||
self.assertEqual(_normalize_vendor(None), "db") |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
While this is better than the last change I still find this naive because I can think of some
WHERE
clause cases this breaks. I wonder if there is a sqlalchemy does this sanitization work more reliably?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.
The idea behind this is that anything which isn't a reserved word will be sanitized. Can you clarify with an example of where clause case which breaks this?
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.
Imagine a scenario
WHERE
clause filter containing spaces and one of these reserved words. How does it behave for the following queryThere 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.
Hmm yes, I see what you're saying. This will result with
SELECT ? FROM table WHERE ? ? ? INDEX ?
. I still think theSELECT ? ?
option is the safest