Skip to content

CLI 3.0.1 add-policy does not support logs #23041

@mason-liu

Description

@mason-liu

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of argocd version.

Describe the bug

Since Argo 3.0.0, from RBAC perspective, logs is not under applications anymore, but current CLI does not support to add logs

To Reproduce

argocd proj role add-policy my-project my-role -a get -p allow -o '*'

Expected behavior

There is only default scope as applications, with v3.0.0, CLI should support logs as well
hardcode here
Screenshots

Version

Paste the output from `argocd version` here.
argocd: v3.0.1+2bcef48
  BuildDate: 2025-05-14T17:01:07Z
  GitCommit: 2bcef4877285db808e47b862567b278c3793d056
  GitTreeState: clean
  GoVersion: go1.24.3
  Compiler: gc
  Platform: darwin/arm64
argocd-server: v3.0.1+2bcef48
  BuildDate: 2025-05-14T15:01:59Z
  GitCommit: 2bcef4877285db808e47b862567b278c3793d056
  GitTreeState: clean
  GoVersion: go1.24.1
  Compiler: gc
  Platform: linux/arm64
  Kustomize Version: v5.6.0 2025-01-14T15:12:17Z
  Helm Version: v3.17.1+g980d8ac
  Kubectl Version: v0.32.2
  Jsonnet Version: v0.20.0

Logs

Paste any relevant application logs here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcomponent:cliIssue related to the Argo CD CLIcomponent:rbacIssue related to User management, Policy and API accessversion:3.0Latest confirmed affected version is 3.0

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions