corestack_ nginx_ rules_ revision_ get
nginx rules revision.
When to use it
Read one nginx rules revision of an environment row: its four hooks and a unified diff per hook against another revision (default the current one); with include_errors, the web error lines logged since it went live.
The answer: revision (its history row and content per hook), against (id, current) and diff per hook (null where the hook agrees). With include_errors, errors: available (false with a reason when the environment's logs cannot be read or the revision never went live), count (every line in the range), from (never older than the logs keep), to and up to 50 lines (at, level, message).
Ask for it
Using the Corefinity MCP server, call corestack_nginx_rules_revision_get with site_id 4211, revision_id 812, include_errors true. (nginx rules revision.) Tell me what it returned.Inputs
Diff against this revision of the row instead of the current one. At least 1.
Also the web error lines since the revision went live (up to 50).
The revision (an id from corestack_nginx_rules_history_list). At least 1.
The environment row. At least 1.
Example call
{
"name": "corestack_nginx_rules_revision_get",
"arguments": {
"site_id": 4211,
"revision_id": 812,
"include_errors": true
}
}If it is refused
| Reason | What to do |
|---|---|
feature_off | include_errors while logs are not available yet. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
Path apps
The answer also carries the revision's path apps: revision.content.path_apps (its records and gates, the whole list as corestack_nginx_rules_update takes it; null when it had none) and diff.path_apps, a unified diff of the two lists written as YAML against the revision named by against (null where they agree).