Skip to content

Define common set of Policy conditions and reasons #1641

Closed
@robscott

Description

@robscott

What would you like to be added:
As part of our policy attachment model, we've defined a standard way of referencing Policies and a recommended structure for all Policy resources. It seems like the natural next step would be to define a set of Conditions that we recommend setting on policy resources to enable more generic tooling to parse different kinds of policies.

Why this is needed:
This will help ensure the status of custom policies can be understood by generic tooling.

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APIkind/featureCategorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions