Feature Request: multi-origin support for cors-allow-origin #5496

matthewhartstonge · 2020-05-03T23:27:22Z

Feature Request

In a world of a single API used by multiple SPAs .... 🌏
It would be really helpful to be able to specify a list of origins/domains/subdomains in the nginx.ingress.kubernetes.io/cors-allow-origin annotation. Especially for subdomains serving media: media1.site.com, media2.site.com, media3.site.com

Intriguingly, this case was put forward in the initial feature request, but looks like it got reduced to an MVP of a single domain? But since the initial merge the thread has continued with many code blocks of how-to config snippet hacks to enable the support of multiple domain handling. This of course gets very messy - especially when having to apply to each microservice's ingress definition.

Linked Issues

Initial Feature Request: #1171

Prior Art?

this comment: Feature Request: CORs to allow specific domain #1171 (comment) ?
traefik: https://docs.traefik.io/middlewares/headers/#cors-headers

/kind feature

The text was updated successfully, but these errors were encountered:

pauln · 2020-05-03T23:45:17Z

As it currently stands, if you attempt to specify a comma-separated list of allowed origins in the nginx.ingress.kubernetes.io/cors-allow-origin annotation, it won't validate and will therefore fall back to the default of *.

This may give the false impression that the list is actually being obeyed, since all listed origins will work... but so will all other origins, since it's ending up as Access-Control-Allow-Origin: *.

bhvishal9 · 2020-06-03T07:44:21Z

Having this feature would be great, we are also struggling to do it. As a workaround, we are using configuration snippet with custom nginx config which is working but still an ugly solution.

jroper · 2020-07-23T03:14:29Z

Here's my ugly configuration snippet to work around:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: foo
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($http_origin ~* "^https?://((?:www\.exactmatch\.com)|(?:.*\.regexmatch\.com))$") {
        set $cors "true";
      }
      if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
      }

      if ($cors = "true") {
        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, PATCH, OPTIONS' always;
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization' always;
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range' always;
      }

      if ($cors = "trueoptions") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, PATCH, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization';
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
      }

ivoribeiro · 2020-08-20T15:14:38Z

Here's my ugly configuration snippet to work around:

apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: foo
  annotations:
    kubernetes.io/ingress.class: "nginx"
    cert-manager.io/cluster-issuer: "letsencrypt-prod"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($http_origin ~* "^https?://((?:www\.exactmatch\.com)|(?:.*\.regexmatch\.com))$") {
        set $cors "true";
      }
      if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
      }

      if ($cors = "true") {
        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, PATCH, OPTIONS' always;
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization' always;
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range' always;
      }

      if ($cors = "trueoptions") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, PATCH, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization';
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
      }

What is the expected behavior in this case if the $http_origin is not on whitelist ?

jroper · 2020-08-31T00:36:59Z

No headers added, which means no CORS policy so all CORS requests blocked by the browser.

kamelotnsk · 2020-09-29T16:53:36Z

Hi all
Here's my configuration snippet to don't work, where is the problem?

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/cors-allow-credentials: "true"
    nginx.ingress.kubernetes.io/enable-access-log: "true"
    nginx.ingress.kubernetes.io/enable-rewrite-log: "true"
    nginx.ingress.kubernetes.io/proxy-body-size: 100m
    ingress.kubernetes.io/force-ssl-redirect: "true"
    nginx.ingress.kubernetes.io/configuration-snippet: |
      if ($http_origin ~* "^https?://((?:ui|uia)\.stand01\.example\.com)$") {
        set $cors "true";
      }
      if ($cors = "true") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Methods' 'GET, PUT, POST, DELETE, PATCH, OPTIONS';
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization';
        add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range';
      }
  name: ui-https-cors-ing
spec:
  tls:
  - hosts: 
    - ui.stand01.example.com
    secretName: stand01-06-example-com-crt-fullchain
  rules:
  - host: ui.stand01.example.com
    http:
      paths:
      - backend:
          serviceName: ui-svc
          servicePort: 8080
        path: /

jfbrennan · 2020-10-22T00:35:39Z

This would be really good!
Currently blocked and having to look into writing a snippet 👎

Support for wildcard subdomains would be really nice:

nginx.ingress.kubernetes.io/cors-allow-origin: "https://*.domain.com"

because "https://app1.domain.com", "https://app2.domain.com", "https://app3.domain.com" all needing to call "https://api.domain.com" is a common need.

shubhrajoy2109 · 2020-11-02T12:40:15Z

Hello Guys,
I am facing Multiple "Access control allow origin" issue while I am using the below mentioned configuration snippet in k8s annotations: -

annotations:
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/configuration-snippet: |
if ($http_origin ~* ((https?://(.+.)*(domain1|domain2).(?:net|com)$)) {
set $cors "true";
}

  # Determine the HTTP request method used
  if ($request_method = 'OPTIONS') {
      set $cors "${cors}options";
  }

  if ($request_method = 'GET') {
      set $cors "${cors}get";
  }

  if ($request_method = 'POST') {
      set $cors "${cors}post";
  }

  if ($cors = "true") {
      # Catch all incase there's a request method we're not dealing with properly
      add_header 'Access-Control-Allow-Origin' "$http_origin";
  }
  if ($cors = "trueget") {
      add_header 'Access-Control-Allow-Origin' "$http_origin";
      add_header 'Access-Control-Allow-Credentials' 'true';
      add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
      add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
  }
  if ($cors = "trueoptions") {
      add_header 'Access-Control-Allow-Origin' "$http_origin";
      #
      # Om nom nom cookies
      #
      add_header 'Access-Control-Allow-Credentials' 'true';
      add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
      #
      # Custom headers and headers various browsers *should* be OK with but aren't
      #
      add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
      #
      # Tell client that this pre-flight info is valid for 20 days
      #
      add_header 'Access-Control-Max-Age' 1728000;
      add_header 'Content-Type' 'text/plain charset=UTF-8';
      add_header 'Content-Length' 0;
      return 204;
  }
  if ($cors = "truepost") {
      add_header 'Access-Control-Allow-Origin' "$http_origin";
      add_header 'Access-Control-Allow-Credentials' 'true';
      add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
      add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
  }

Please find the attached error: -

Please suggest where am I doing wrong.

jony89 · 2021-01-20T11:07:22Z

The problem with the workaround:

nginx.ingress.kubernetes.io/configuration-snippet: |
   add_header 'Access-Control-Allow-Origin' "$http_origin";
   .....

is that in case the pod is down for some reason, these headers will not be included and the request will be blocked instead of getting 503. so you must add always see #6782

        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Credentials' "true" always;
        add_header 'Access-Control-Allow-Methods' "PUT, GET, POST, DELETE, OPTIONS" always;
        add_header 'Access-Control-Allow-Headers' "DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization" always;
        if ($request_method = 'OPTIONS') { 
          add_header 'Access-Control-Allow-Origin' "$http_origin" always;
          add_header 'Access-Control-Allow-Credentials' "true" always;
          add_header 'Access-Control-Allow-Methods' "PUT, GET, POST, DELETE, OPTIONS" always;
          add_header 'Access-Control-Allow-Headers' "DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Authorization" always;
          add_header 'Access-Control-Max-Age' 1728000 always;
          return 204;
        }

hipages-leimiao · 2021-03-03T03:03:25Z

What is the expected behavior in this case if the $http_origin is not on whitelist ?

This is a case:
https://stackoverflow.com/questions/19743396/cors-cannot-use-wildcard-in-access-control-allow-origin-when-credentials-flag-i

matteocusinato · 2021-05-12T09:14:44Z

Hi, any news for CORS support for wildcard subdomains?

tokers · 2021-05-12T11:03:22Z

CORS support for wildcard subdomains

Welcome to submit a new issue to track it.

jfbrennan · 2021-05-13T05:05:31Z

CORS support for wildcard subdomains

Welcome to submit a new issue to track it.

@tokers this is the issue "Feature Request: multi-origin support for cors-allow-origin". The op suggested comma-separated list, I suggested wildcard subdomains, or maybe both? I don't think any of us really care that much about those differences we just want a simple way to get multi-origin support w/o writing snippets.

tokers · 2021-05-14T04:32:04Z

CORS support for wildcard subdomains

Welcome to submit a new issue to track it.

Ignore this message, I'm not sorry that I misunderstood some stuff there.

tokers · 2021-05-14T04:33:55Z

Extend the cors-allow-origin to be a comma-separated string so that multiple origins can be supported is a good point, I will look through the current code base and judge whether this is feasible, if so, I will submit a PR to support it, or, I will explain the reason here.

tokers · 2021-05-14T04:33:59Z

/assign

tokers · 2021-05-14T08:33:22Z

See #7134 for details :)

iamNoah1 · 2021-08-03T15:26:54Z

@matthewhartstonge @tokers can we consider to close this one?

matthewhartstonge · 2021-08-03T21:31:33Z

@iamNoah1 hmm, I think we're going to have to go with no...

tokers · 2021-08-04T02:10:56Z

@matthewhartstonge @tokers can we consider to close this one?

PR was reverted as the implementation is not right 😂

jfbrennan · 2021-08-04T06:04:19Z

@tokers It has to resolve to a single origin or *. What we're asking for is some magic that does this resolution for us either from a csv or regex.

constb · 2021-08-13T14:19:33Z

I think this needs to change:

ingress-nginx/internal/ingress/annotations/cors/main.go

Line 39 in 807fd69

    
           corsOriginRegex = regexp.MustCompile(`^(https?://[A-Za-z0-9\-\.]*(:[0-9]+)?|\*)?$`)

gtskaushik · 2021-08-17T14:25:21Z

This is a much needed implementation

iamNoah1 · 2021-08-17T14:39:49Z

@tokers @matthewhartstonge @jfbrennan @constb @gtskaushik we accept and are happy for any contributions.

arvtiwar · 2021-09-05T15:33:59Z

Yep, we are also looking for this capability.

arvtiwar · 2021-09-05T16:36:40Z

Hi Guys, please suggest how to achieve this use case. We have Cloudflare, which proxies all the requests to our backend based on K8S Nginx ingress. We need to support multiple subdomains (subd01.mydomain.com, subd02.mydomain.com, .....) for our clients, and all should hit the same API backend (api.mydomain.com).
Any workaround/idea how to address it? Thanks in advance

iamNoah1 · 2021-09-08T09:46:50Z

/help

k8s-ci-robot · 2021-09-08T09:46:51Z

@iamNoah1:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

larivierec · 2021-09-09T03:17:04Z

I have no idea if this is a good way to do it but it works. Let me know if there is something that can be done better.

#7614

arvtiwar · 2021-09-09T10:18:17Z

IMHO, below are the two solutions wd be perfect

there has to be a way to enforce user-defined policy (e.g. nginx.ingress.kubernetes.io/cors-allow-origin-policy: "user-defined regex") to match "http_origin"
User should list all the subdomains (foo.bar.com, foo1.bar.com, yar.bar.com, bkar.foo.bar.com ......) in NginX ConfigMap for ingress to exact match.

AlbertMarashi · 2021-10-16T11:04:34Z

Any news?

jfbrennan · 2021-10-21T18:01:50Z

@arvtiwar there are enterprises where that list would be HUGE. Being able to * is really important and it looks like the PR supports that

* Add Initial support for multiple cors origins in nginx - bump cluster version for `make dev-env` - add buildOriginRegex function in nginx.tmpl - add e2e 4 e2e tests for cors.go - refers to feature request #5496 * add tests + use search to identify '*' origin * add tests + use search to identify '*' origin Signed-off-by: Christopher Larivière <lariviere.c@gmail.com> * fix "should enable cors test" looking at improper values * Modify tests and add some logic for origin validation - add origin validation in cors ingress annotations - add extra tests to validate regex - properly escape regex using "QuoteMeta" - fix some copy/paste errors * add TrimSpace and length validation before adding a new origin * modify documentation for cors and remove dangling comment * add support for optional port mapping on origin * support single-level wildcard subdomains + tests * Remove automatic `*` fonctionality from incorrect origins - use []string instead of basic string to avoid reparsing in template.go - fix typo in docs - modify template to properly enable only if the whole block is enabled - modify cors parsing - test properly by validating that the value returned is the proper origin - update unit tests and annotation tests * Re-add `*` when no cors origins are supplied + fix tests - fix e2e tests to allow for `*` - re-add `*` to cors parsing if trimmed cors-allow-origin is empty (supplied but empty) and if it wasn't supplied at all. * remove unecessary logic for building cors origin + remove comments - add some edge cases in e2e tests - rework logic for building cors origin there was no need for logic in template.go for buildCorsOriginRegex if there is a `*` it ill be short-circuited by first if. if it's a wildcard domain or any domain (without a wildcard), it MUST match the main/cors.go regex format. if there's a star in a wildcard domain, it must be replaced with `[A-Za-z0-9]+` * add missing check in e2e tests

larivierec · 2021-11-03T13:54:33Z

merged, but build isn't ready yet.

larivierec · 2021-11-06T02:13:19Z

/assign

villesau · 2021-11-10T19:23:25Z

@larivierec just stumbled upon this issue. Any timeline for the release? :)

larivierec · 2021-11-10T19:35:08Z

you'll have to wait for the official release from the maintainer @rikatz
it should be soon

Update: I'll close once version is released

k8s-ci-robot · 2021-11-16T02:06:35Z

@larivierec: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

rikatz · 2021-11-16T02:30:48Z

/close
Thanks :)

k8s-ci-robot · 2021-11-16T02:31:11Z

@rikatz: Closing this issue.

In response to this:

/close
Thanks :)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

patsevanton · 2022-09-30T13:55:02Z

Please share code with multi-origin support for cors-allow-origin

kszafran · 2022-09-30T13:57:50Z

Please share code with multi-origin support for cors-allow-origin

You can now specify multiple, comma-separated domains in cors-allow-origin, e.g.:

nginx.ingress.kubernetes.io/cors-allow-origin: "https://example.com, https://another.com, http://localhost:8000"

* Add Initial support for multiple cors origins in nginx - bump cluster version for `make dev-env` - add buildOriginRegex function in nginx.tmpl - add e2e 4 e2e tests for cors.go - refers to feature request kubernetes#5496 * add tests + use search to identify '*' origin * add tests + use search to identify '*' origin Signed-off-by: Christopher Larivière <lariviere.c@gmail.com> * fix "should enable cors test" looking at improper values * Modify tests and add some logic for origin validation - add origin validation in cors ingress annotations - add extra tests to validate regex - properly escape regex using "QuoteMeta" - fix some copy/paste errors * add TrimSpace and length validation before adding a new origin * modify documentation for cors and remove dangling comment * add support for optional port mapping on origin * support single-level wildcard subdomains + tests * Remove automatic `*` fonctionality from incorrect origins - use []string instead of basic string to avoid reparsing in template.go - fix typo in docs - modify template to properly enable only if the whole block is enabled - modify cors parsing - test properly by validating that the value returned is the proper origin - update unit tests and annotation tests * Re-add `*` when no cors origins are supplied + fix tests - fix e2e tests to allow for `*` - re-add `*` to cors parsing if trimmed cors-allow-origin is empty (supplied but empty) and if it wasn't supplied at all. * remove unecessary logic for building cors origin + remove comments - add some edge cases in e2e tests - rework logic for building cors origin there was no need for logic in template.go for buildCorsOriginRegex if there is a `*` it ill be short-circuited by first if. if it's a wildcard domain or any domain (without a wildcard), it MUST match the main/cors.go regex format. if there's a star in a wildcard domain, it must be replaced with `[A-Za-z0-9]+` * add missing check in e2e tests

xtianus79 · 2024-06-28T14:22:14Z

thanks this feature worked great!!!

matthewhartstonge added the kind/feature Categorizes issue or PR as related to a new feature. label May 3, 2020

matthewhartstonge changed the title ~~Feature Request:~~ Feature Request: multi-origin support for cors-allow-origin May 3, 2020

sshi100 mentioned this issue Dec 1, 2020

247 add dev env commitdev/zero-backend-go#45

Merged

jony89 mentioned this issue Jan 20, 2021

nginx snippet headers are not passed when pod is down #6782

Closed

k8s-ci-robot assigned tokers May 14, 2021

tokers mentioned this issue May 14, 2021

feat: multiple-cors-allow-origin support #7134

Merged

8 tasks

maxisam mentioned this issue May 26, 2021

cors-allow-origin - use more than 1 URL jcmoraisjr/haproxy-ingress#477

Closed

k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 8, 2021

larivierec mentioned this issue Sep 8, 2021

Support cors-allow-origin with multiple origins #7614

Merged

8 tasks

k8s-ci-robot assigned larivierec Nov 6, 2021

k8s-ci-robot closed this as completed Nov 16, 2021

noahwsmith mentioned this issue May 13, 2024

Being able to set CORS with a .env variable would be nice Islandora-Devops/isle-buildkit#333

Closed

Feature Request: multi-origin support for cors-allow-origin #5496

Feature Request: multi-origin support for cors-allow-origin #5496

Comments

matthewhartstonge commented May 3, 2020 • edited Loading

Feature Request

Linked Issues

Prior Art?

pauln commented May 3, 2020

bhvishal9 commented Jun 3, 2020

jroper commented Jul 23, 2020

ivoribeiro commented Aug 20, 2020

jroper commented Aug 31, 2020

kamelotnsk commented Sep 29, 2020 • edited Loading

jfbrennan commented Oct 22, 2020 • edited Loading

shubhrajoy2109 commented Nov 2, 2020 • edited Loading

jony89 commented Jan 20, 2021 • edited Loading

hipages-leimiao commented Mar 3, 2021 • edited Loading

matteocusinato commented May 12, 2021

tokers commented May 12, 2021 • edited Loading

jfbrennan commented May 13, 2021 • edited Loading

tokers commented May 14, 2021

tokers commented May 14, 2021

tokers commented May 14, 2021

tokers commented May 14, 2021

iamNoah1 commented Aug 3, 2021

matthewhartstonge commented Aug 3, 2021

tokers commented Aug 4, 2021

jfbrennan commented Aug 4, 2021

constb commented Aug 13, 2021

gtskaushik commented Aug 17, 2021

iamNoah1 commented Aug 17, 2021 • edited Loading

arvtiwar commented Sep 5, 2021

arvtiwar commented Sep 5, 2021

iamNoah1 commented Sep 8, 2021

k8s-ci-robot commented Sep 8, 2021

larivierec commented Sep 9, 2021 • edited Loading

arvtiwar commented Sep 9, 2021

AlbertMarashi commented Oct 16, 2021

jfbrennan commented Oct 21, 2021

larivierec commented Nov 3, 2021

larivierec commented Nov 6, 2021

villesau commented Nov 10, 2021

larivierec commented Nov 10, 2021 • edited Loading

k8s-ci-robot commented Nov 16, 2021

rikatz commented Nov 16, 2021

k8s-ci-robot commented Nov 16, 2021

patsevanton commented Sep 30, 2022

kszafran commented Sep 30, 2022 • edited Loading

xtianus79 commented Jun 28, 2024

matthewhartstonge commented May 3, 2020 •

edited

Loading

kamelotnsk commented Sep 29, 2020 •

edited

Loading

jfbrennan commented Oct 22, 2020 •

edited

Loading

shubhrajoy2109 commented Nov 2, 2020 •

edited

Loading

jony89 commented Jan 20, 2021 •

edited

Loading

hipages-leimiao commented Mar 3, 2021 •

edited

Loading

tokers commented May 12, 2021 •

edited

Loading

jfbrennan commented May 13, 2021 •

edited

Loading

iamNoah1 commented Aug 17, 2021 •

edited

Loading

larivierec commented Sep 9, 2021 •

edited

Loading

larivierec commented Nov 10, 2021 •

edited

Loading

kszafran commented Sep 30, 2022 •

edited

Loading