Skip to content

[RUN4247] Enforce project-level authorization on execution metrics API - #1912

Open
ronaveva wants to merge 2 commits into
4.0.xfrom
RUN-4247
Open

[RUN4247] Enforce project-level authorization on execution metrics API#1912
ronaveva wants to merge 2 commits into
4.0.xfrom
RUN-4247

Conversation

@ronaveva

@ronaveva ronaveva commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

This pull request updates the API documentation to clarify the authorization requirements for accessing execution metrics. The new section explains in detail how access is determined based on the project and query parameters.

Documentation update:

  • Added a section specifying that read access for the event resource type is required to obtain execution metrics, with clear rules for project-specific, job-filtered, and global queries, and how authorization affects the results and error responses.

OSS PR related: https://github.com/rundeck/rundeck/pull/10419

@ronaveva ronaveva added this to the 6.2.0 milestone Aug 3, 2026
@ronaveva
ronaveva requested review from a team, Copilot and fdevans August 3, 2026 18:01

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates the Rundeck API documentation to describe the project-scoped authorization rules enforced by the Execution Metrics endpoints, including how the project and jobIdListFilter inputs affect access and results.

Changes:

  • Documented required read permission on the event resource type for execution metrics queries.
  • Clarified authorization behavior for project-scoped, job-filtered, and global (no project) metrics queries, including when 403 responses occur.

Comment thread docs/api/index.md Outdated
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
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