Repository navigation
Dependency check on sre extension startup #32
Description
All dependencies like:
- Python libraries to geenrate graphs
- Markdown parsing tool agents are using etc.
- CLI and MCP tools used for interactions with GCP
Should be checked at sre extension installation and setup to prevent unwanted and non-transparent installations while interacting with sre extension.
Activity
github-actions commentedon Jun 1, 2026
🤖 Hi @SzymonSt, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.
github-actions commentedon Jun 1, 2026
🤖 I'm sorry @SzymonSt, but I was unable to process your request. Please see the logs for more details.
palladius commentedon Jun 1, 2026
please explain better what u mean. some are easy, Unit Tests. Something you say require an installation and a real scenario, project id, ... setup so its doable but its >1wk work.
i think the work we're doing for the evals will give us this for free, so IIMHO this is a dupe of the EVAL bug, no?
SzymonSt commentedon Jun 1, 2026
Not really, this is the following User Journey:
It would be better for
just install agyto check if these exist before-hand, more transparent, gaining users trust from day 1.Tests are sth different.
palladius commentedon Jun 1, 2026
I see now.
So what you suggest is to install
uv. I think we should document in the README thatuvis a prerequisite to it.You're absolutely right. All my skills use
uvas a prerequisite and from what I hear the whole world is moving to uv as python3 and virtualenv are suboptimal.palladius commentedon Jun 2, 2026
I think we shikd be more explicit that people need to have:
We should also ad an EVAL which checks for further dependencies. i think bash+python are sufficient in ALL.
SzymonSt commentedon Aug 2, 2026
New dependency to take into account: standalone graphviz -
dotCLI