Skip to content

Think about how we want the dangerous ownership override flag and the allowed apps flag to interact #997

@100mik

Description

@100mik

Describe the problem/challenge you have
As of today, I am required to supply the dangerous flag even after specifying apps we are okay with snatching ownership from.

Describe the solution you'd like
Food for thought:

  1. Does it make sense to not require the dangerous flag while supplying app names explicitly?
  2. Should we mark the flag we supply specific names as dangerous? Or is it not because the user is being specific here?

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    carvel acceptedThis issue should be considered for future work and that the triage process has been completeddiscussionThis issue is not a bug or feature and a conversation is needed to find an appropriate resolutionenhancementThis issue is a feature request

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions