Skip to content

BREAKING CHANGE: fix: Set correct access level check for ZOWE APIML.SERVICES resource - #5025

Draft
pavel-jares-bcm wants to merge 3 commits into
v3.x.xfrom
reboot/ZOWESERVER_ZOWE_API-LAYER_V3-X_X-002
Draft

pavel-jares-bcm wants to merge 3 commits into
v3.x.xfrom
reboot/ZOWESERVER_ZOWE_API-LAYER_V3-X_X-002

Conversation

@pavel-jares-bcm

Copy link
Copy Markdown
Contributor

Description

There are inconsistency in using security check. The aim is to use READ level for endpoint that only fetch data and UPDATE for others where data are updated (revoking PAT is also modification).

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

  • fix: Bug fix (non-breaking change which fixes an issue)
  • BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the style guidelines of this project
  • PR title conforms to commit message guideline ## Commit Message Structure Guideline
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

Signed-off-by: Pavel Jareš <Pavel.Jares@broadcom.com>
@github-actions github-actions Bot added the invalid This doesn't seem right label Oct 16, 2026
@github-actions

Copy link
Copy Markdown

It looks like PR title does not contain one of the required prefixes: fix:, feat:, docs:, refactor:, chore:. Please add one of the prefixes based on the type of your changes by following our contributing guidelines

@sonarqubecloud

Copy link
Copy Markdown

@richard-salac richard-salac added this to the 4.0 milestone Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right size/S V4

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants