-
Notifications
You must be signed in to change notification settings - Fork 127
tags for mcp images #20035
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
base: master
Are you sure you want to change the base?
tags for mcp images #20035
Conversation
trigger: test-robottelo |
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.
Hey there - I've reviewed your changes - here's some feedback:
Blocking issues:
- Detected possible formatted SQL query. Use parameterized queries instead. (link)
- Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option. (link)
General comments:
- Avoid hardcoding the tag value ("6.18") in the function—make the version tag configurable via settings or an environment variable so it stays in sync with future image updates.
- The run_cmd uses
image_name
, but it isn’t explicitly tagged—ensureimage_name
includes the same tag you pull (or append:{tag}
) to prevent pulling one version and running another. - Re-adding a
.strip()
(or otherwise normalizing whitespace) on the multilinerun_cmd
string can help avoid unintended spaces or newlines when executing the command.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Avoid hardcoding the tag value ("6.18") in the function—make the version tag configurable via settings or an environment variable so it stays in sync with future image updates.
- The run_cmd uses `image_name`, but it isn’t explicitly tagged—ensure `image_name` includes the same tag you pull (or append `:{tag}`) to prevent pulling one version and running another.
- Re-adding a `.strip()` (or otherwise normalizing whitespace) on the multiline `run_cmd` string can help avoid unintended spaces or newlines when executing the command.
## Individual Comments
### Comment 1
<location> `pytest_fixtures/component/mcp.py:79` </location>
<code_context>
assert target_sat.execute(pull_cmd).status == 0
</code_context>
<issue_to_address>
**security (python.lang.security.audit.formatted-sql-query):** Detected possible formatted SQL query. Use parameterized queries instead.
*Source: opengrep*
</issue_to_address>
### Comment 2
<location> `pytest_fixtures/component/mcp.py:79` </location>
<code_context>
assert target_sat.execute(pull_cmd).status == 0
</code_context>
<issue_to_address>
**security (python.sqlalchemy.security.sqlalchemy-execute-raw-query):** Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option.
*Source: opengrep*
</issue_to_address>
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
PRT Result
|
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.
New security issues found
trigger: test-robottelo |
PRT Result
|
trigger: test-robottelo |
PRT Result
|
Problem Statement
downstream registry no longer picks latest when no tag is specified
Solution
specifying tags explicitely
Related Issues