`kapp deploy --diff-run` should not require updating the existing ConfigMap

[Anshul Sirur]

What steps did you take:

• Executed kapp deploy --app "svc-kapp" --diff-run -f kapp.yaml for an existing app svc-kapp.

What happened:

• Error:

kapp: Error: Updating app: configmaps "svc-kapp" is forbidden:

  User "xxxxx" cannot update resource "configmaps" in API group "" in the namespace "svc"

What did you expect:

• A diff of the changes to be displayed with no errors and no further action.

Anything else you would like to add:

• My primary use case for this feature is displaying configuration changes raised in a pull request or on a branch during which CI should have read-only permissions in the cluster.

Environment:

• kapp version (use kapp --version): v0.58.0
• OS (e.g. from /etc/os-release): Ubuntu 22.04 LTS (GitHub Actions)
• Kubernetes version (use kubectl version): v1.24.15

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.