Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wasm configuration based on extensions #867

Open
eguzki opened this issue Sep 20, 2024 · 0 comments · May be fixed by #868
Open

Wasm configuration based on extensions #867

eguzki opened this issue Sep 20, 2024 · 0 comments · May be fixed by #868
Assignees
Labels
area/api Changes user facing APIs
Milestone

Comments

@eguzki
Copy link
Contributor

eguzki commented Sep 20, 2024

The wasm configuration has changed. Still WIP in branch external-auth and related PR:

New configuration, based on extensions, looks like the following:

---
extensions:
  limitador:
    type: ratelimit
    endpoint: limitador-cluster
    failureMode: deny
policies:
  - name: rlp-ns-A/rlp-name-A
    hostnames:
      - '*.toystore.com'
      - example.com
    rules:
      - conditions:
          - allOf:
              - selector: request.path
                operator: eq
                value: /admin/toy
              - selector: request.method
                operator: eq
                value: POST
              - selector: request.host
                operator: eq
                value: cars.toystore.com
        actions:
          - extension: limitador
            scope: rlp-ns-A/rlp-name-A
            data:
              - static:
                  key: rlp-ns-A/rlp-name-A
                  value: "1"
              - selector:
                  selector: auth.metadata.username

The wasm controllers should be updated to generate the configuration scheme expected by the wasm module.

The scope of this issue is limited to rate limiting. External auth using wasm will be covered in following up tasks.

Related issues: Kuadrant/wasm-shim#58

@eguzki eguzki added this to the Kuadrant v1 milestone Sep 20, 2024
@eguzki eguzki self-assigned this Sep 20, 2024
@eguzki eguzki added the area/api Changes user facing APIs label Sep 20, 2024
@eguzki eguzki linked a pull request Sep 23, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Changes user facing APIs
Projects
Status: Ready For Review
Development

Successfully merging a pull request may close this issue.

1 participant