Skip to content

Handling secret references during policy merges #8094

@kkk777-7

Description

@kkk777-7

Fixed and added. Though I realised as part of fixing it that when merging security policies that use secrets on the Gateway, the secret has to exist in the Route using it as well. I have added a note in the documentation for it. Will try and see if I can fix that subsequent to this change merging in.

Originally posted by @rajatvig in #7918 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions