Skip to content

Change call_foreman_api_get 'params' type from dict to JSON string (rebased)#87

Open
schuellerf wants to merge 2 commits into
theforeman:developfrom
schuellerf:rebase_pr_78
Open

Change call_foreman_api_get 'params' type from dict to JSON string (rebased)#87
schuellerf wants to merge 2 commits into
theforeman:developfrom
schuellerf:rebase_pr_78

Conversation

@schuellerf

@schuellerf schuellerf commented Feb 16, 2026

Copy link
Copy Markdown

Just trying to push this due to PTO
@shzhou12 I hope this is fine for you 😇🙏🙇‍♂️

This rebases #78 onto origin/develop as of now & fixes the ruff check

-- original PR description --
Updated the 'params' argument in the call_foreman_api_get function to expect a string (JSON format) instead of a dictionary. This ensures compatibility with MCP client like Langflow.

shzhou12 and others added 2 commits February 16, 2026 13:25
Updated the 'params' argument in the call_foreman_api_get function to
expect a string (JSON format) instead of a dictionary. This ensures
compatibility with MCP client like Langflow.
Use double-quoted string for the JSON example to satisfy ruff format.
@schuellerf
schuellerf requested a review from a team as a code owner February 16, 2026 12:42
description="Calls GET action on Foreman API.",
description=(
"Calls GET action on Foreman API. "
"The 'params' argument must be a JSON string representing "

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd vote against that, especially if it's mandates the client to send a JSON string only given that this is mostly a workaround for only one (?) client (which is also its issue and should be solved there)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants