alexsnaps/gw-policies-playground

gw-policies-playground's Issues

Add host et al to GW-API mocks

The mock structs for the Gateway API Gateway and Route resources currently do not define the routing/filtering properties:

• Gateway: hostname
• HTTPRoute: hostnames and route matchers path, headers, queryParams and method

These are especially needed to write tests for deciding when a merger between policies is needed, provided the policies target distinct network resources that are strict subsets one of another.

Tests for policies targeting wildcard/hostnames and analogous

For cases that involving deciding on merging or not policies that target network resources that are strict subsets one of another. E.g.:

• Policy A → Gateway: hostname="*.acme.com"
• Policy B → HTTPRoute: headers{name="Authorization", type=RegularExpression, value="Bearer .+"}

Depending on the intent, the following variations might be possible:

1. Policy A merge overrides Policy B
2. Policy A merges providing defaults to Policy B
3. Policy A is accepted and Policy B is discarded (no merger)
4. Policy A is discarded and Policy B is accepted (no merger)
5. Policy A and Policy B are both accepted (no merger)

Depends on #3.