feat: add support for externalized consumers #7657

jschmid1 · 2024-07-18T16:26:17Z

Description

Testing instructions

Preview link:

Checklist

Review label added
Conditional version tags added, if applicable.

netlify · 2024-07-18T16:26:33Z

✅ Deploy Preview for kongdocs ready!

Name	Link
🔨 Latest commit	`a3f84e0`
🔍 Latest deploy log	https://app.netlify.com/sites/kongdocs/deploys/67dc2574cdfac00008637459
😎 Deploy Preview	https://deploy-preview-7657--kongdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	9 paths audited Performance: 92 (🟢 up 1 from production) Accessibility: 93 (no change from production) Best Practices: 98 (🟢 up 8 from production) SEO: 99 (no change from production) PWA: - View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

mheap · 2024-08-19T16:30:20Z

app/_hub/kong-inc/key-auth/overview/_index.md

+  - geo: null
+    id: null


geo and id should be optional (default null) imo

Guaris · 2024-08-19T18:12:14Z

app/_hub/kong-inc/key-auth/overview/_index.md

+
+-- Dummy/Link that points to Konnect Docs when ready.
+
+With the `pool_id` you obtained from the previous step, you can configure the key-auth plugin to validate API keys against the Identity Service.


@jschmid1 where does the pool_id come from? Konnect?

smritikjaggi

We need to change all references of pools to realms, and update the field terminology

smritikjaggi · 2024-09-09T17:41:27Z

app/_hub/kong-inc/key-auth/how-to/_index.md

@@ -0,0 +1,71 @@
+---
+nav_title: 
+title: How to configure pools


Change to Realms

smritikjaggi · 2024-09-09T17:42:05Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+---
+
+
+With `pool_id` you can configure the key-auth plugin to validate API keys against the Identity Service.


Change to "realm_id"

smritikjaggi · 2024-09-09T17:42:25Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+With `pool_id` you can configure the key-auth plugin to validate API keys against the Identity Service.
+
+### Configuring Multiple Pools


change to "Realms"

smritikjaggi · 2024-09-09T17:42:39Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+### Configuring Multiple Pools
+
+In the key-auth plugin configuration, add the `pools` option as shown below:


change to "realms"

smritikjaggi · 2024-09-09T17:43:14Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+In the key-auth plugin configuration, add the `pools` option as shown below:
+
+```yaml
+pools:


change to "identity_realms"

smritikjaggi · 2024-09-09T17:46:49Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+    type: remote
+```
+
+In this configuration, the dataplane will initially check the local pool (LMDB) before querying the remote Identity Service.


cp-scoped consumers first

smritikjaggi · 2024-09-09T17:46:58Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+In this configuration, the dataplane will initially check the local pool (LMDB) before querying the remote Identity Service.
+
+If a matching key is found in any of these pools, the request will be authenticated. If the key is not found in any of the configured pools, the request will be blocked.


smritikjaggi · 2024-09-09T17:47:08Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+If a matching key is found in any of these pools, the request will be authenticated. If the key is not found in any of the configured pools, the request will be blocked.
+
+### Configuring Single Pools


Single Realm

smritikjaggi · 2024-09-09T17:50:04Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+### Configuring Single Pools
+
+It is also possible to configure only a single pool, either local or remote. However, only one of each type can be configured.


change pool to realm
change "either local or remote" to "consumers can be scoped to the geo or cp".

smritikjaggi · 2024-09-09T17:50:18Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+
+It is also possible to configure only a single pool, either local or remote. However, only one of each type can be configured.
+
+To configure only a remote pool:


change "remote pool" to "realm"

Testing edit function

Updated the terminology used for realms and the yaml file examples

…in to add realms section Signed-off-by: Diana <[email protected]>

cloudjumpercat · 2025-03-11T21:01:47Z

@brentos Hi! I just wanted to let you know I'll be working on external consumers and I just added some changes to the PR, including a new Konnect page that explains what they are and how to configure them, as well as a revised section to key auth. I had a few questions while I was working on it:

We mention that a kong dev build is required, but this is for Konnect. I don't understand how that custom dev build is required unless we're using it for data plane nodes?
I tried using the /realms endpoint, but wasn't able to access it. Maybe something to do with not having the custom build?
Are we publishing the API specs for this release? Can I have a copy of them so I can look at the endpoints and parameters?
So key auth only associates the plugin with a realm, it doesn't actually create the realm, you use the /realm endpoint to do that?

Signed-off-by: Diana <[email protected]>

cloudjumpercat · 2025-03-13T15:31:47Z

Broken sales link was a false failure, I manually approved link validation for now

Signed-off-by: Diana <[email protected]>

cloudjumpercat · 2025-03-13T20:12:50Z

@smritikjaggi and @brentos The externalized consumers pages are ready for review if you have the chance to look them over:

lena-larionova · 2025-03-13T21:38:09Z

app/konnect/centralized-consumers.md

+
+The following diagram shows how you can configure centralized Consumers in realms as well as scope Consumers to a Control Plane:
+
+<!--vale off -->


I don't really understand what this diagram is showing me.
For example:

Consumer: Ira
Consumer Groups: Gold for appointments

Does this consumer only have access to the appointments control plane? Or does it have access to both control planes, but since the consumer group Gold only exists on appointments, it can only access appointments? Or something else?

Are control planes located inside realms, or alongside them?

app/konnect/centralized-consumers.md

lena-larionova · 2025-03-13T21:49:26Z

app/konnect/centralized-consumers.md

+* The Consumer identity can be setup centrally instead of being defined across multiple control planes.
+* Share Consumers across multiple control planes. Users don't need to replicate changes to Consumer identity in multiple control planes and Consumer configuration doesn't conflict.
+* Reduces configuration sync issues between the control plane and the dataplane. Centralized Consumers aren't part of the configuration that is pushed down from the control plane to the dataplane, so it reduces config size and latency. 
+


Maybe add the required Gateway version here as a note, somewhere.

app/_hub/kong-inc/key-auth/overview/_index.md

lena-larionova · 2025-03-13T21:52:41Z

app/_hub/kong-inc/key-auth/overview/_index.md

+* **Realm is listed first:** The dataplane will first reach out to the realm. If the API key is not found in the realm, the dataplane will look for the API key in the control plane config. 
+* **Control Plane scope listed first:** The dataplane will initially check the control plane configuration (LMDB) for the API key before looking up the API Key in the realm.
+* **Realm isn't associated with a control plane:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.
+* **Realm is only associated with a Control Plane:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.


Suggested change

* **Realm is listed first:** The dataplane will first reach out to the realm. If the API key is not found in the realm, the dataplane will look for the API key in the control plane config.

* **Control Plane scope listed first:** The dataplane will initially check the control plane configuration (LMDB) for the API key before looking up the API Key in the realm.

* **Realm isn't associated with a control plane:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.

* **Realm is only associated with a Control Plane:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.

* **Realm is listed first:** The data plane will first reach out to the realm. If the API key is not found in the realm, the data plane will look for the API key in the control plane config.

* **Control Plane scope listed first:** The data plane will initially check the control plane configuration (LMDB) for the API key before looking up the API Key in the realm.

* **Realm isn't associated with a control plane:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the data plane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.

* **Realm is only associated with a Control Plane:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the data plane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.

Should this info actually be on the Konnect page instead, except genericized to "credentials" instead of "API key"?

app/konnect/centralized-consumers.md

mheap · 2025-03-14T12:44:33Z

app/konnect/centralized-consumers.md

+<!--vale off -->
+{% mermaid %}
+flowchart TD
+A(Consumer: Cruz<br>Consumer Groups: Gold for appointments, Silver for billing)


Each consumer can be in multiple consumer groups, but you can't scope the consumer group to a service.

If billing respected the Gold group, then Cruz would be Gold for billing too.

mheap · 2025-03-14T12:45:43Z

app/konnect/centralized-consumers.md

+   * {region}: Region for your {{site.konnect_short_name}} instance.
+   * $KONNECT_TOKEN: Replace with your {{site.konnect_short_name}} personal access token.
+   * $CONTROL_PLANE_UUID: (Optional) Replace with your Control Plane UUID.
+   * `ttl` and `negative_ttl`: (Optional) Time-to-live in minutes of the consumer or negative consumer for this realm in the {{site.base_gateway}} cache.


What's a negative consumer? I don't think that this is what negative_ttl means. @zekth can you help us out here?

there's no concept of negative_consumer. negative_ttl represents the TTL of a bad login cache entry. Meaning api key foobar is sent to the gateway; gateway reaches the service to authenticate it; if it fails the api key foobar will be labelled as non working in gateway cache to the time of the TTL. During that time it won't try to reache the authentication server.

mheap · 2025-03-14T12:47:10Z

app/konnect/centralized-consumers.md

+   * $KONNECT_TOKEN: Replace with your {{site.konnect_short_name}} personal access token.
+   * {realmId}: The ID of the realm you created previously. 
+   * $CONSUMER_NAME: Replace with the name of the consumer.
+   * $CONSUMER_GROUP: (Optional) Replace with the name of the consumer groups you want to associate with the consumer.


If I specify consumer_groups on a consumer does that replace consumer_groups from the realm, or are they added together?

If I specify consumer_groups: [] does that mean no consumer groups, or use the groups from the realm?

This is additive here, I'll add that info to the doc.

mheap · 2025-03-14T12:49:34Z

app/_hub/kong-inc/key-auth/overview/_index.md

+* **Realm isn't associated with a control plane:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.
+* **Realm is only associated with a Control Plane:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.


Suggested change

* **Realm isn't associated with a control plane:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.

* **Realm is only associated with a Control Plane:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.

* **Realm only:** You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.

* **Control Plane only:** You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.

mheap · 2025-03-14T12:50:22Z

app/_hub/kong-inc/key-auth/overview/_index.md

@@ -287,19 +295,55 @@ Response:
 }
 ```

+{% if_version gte: 3.10.x %}
+
+## Configure realms for centralized Consumers in {{site.konnect_short_name}}


Should this be an example rather than on the overview?

Good point, I'll convert it to an example.

Co-authored-by: lena-larionova <[email protected]>

Signed-off-by: Diana <[email protected]>

app/_hub/kong-inc/key-auth/how-to/_index.md

smritikjaggi

The content looks good Diana! Can we talk through the naming and placement of Consumers please? This doc outlines that we decided to go with Consumers as the official naming of this initiative: https://docs.google.com/document/d/1k-d9FqAk4Jqo-e9-19IekqKQlNWfaFdgBNBuJGBw80k/edit?tab=t.0#heading=h.tn4g33ltt5z7

smritikjaggi · 2025-03-19T05:37:16Z

app/_data/docs_nav_konnect.yml

@@ -15,6 +15,8 @@
          url: /private-connections/aws-privatelink/
    - text: Geographic Regions
      url: /geo/
+    - text: Regional Consumers


We are going with the naming of "Consumers" as we are not introducing a new entity, but are expanding on the existing Consumer entity such that they can be defined in a central location per region and referenced across multiple control planes. Doc: https://docs.google.com/document/d/1k-d9FqAk4Jqo-e9-19IekqKQlNWfaFdgBNBuJGBw80k/edit?tab=t.0#heading=h.tn4g33ltt5z7

Sounds good! I'll revise this to call out that this is a new type of consumer management.

smritikjaggi · 2025-03-19T05:40:34Z

app/_hub/kong-inc/key-auth/how-to/_index.md

+title: Configure realms for regional Consumers in {{site.konnect_short_name}}
+---
+
+Starting in {{site.base_gateway]] 3.10.x, credentials that are stored centrally in {{site.konnect_short_name}} that are shared across multiple {{site.base_gateway}} can be validated by configuring `identity_realms` field in the Key Auth plugin. You can use these realms when you create [regional Consumers](/konnect/regional-consumers/).


Do we want to add some language that says "today a DP can only reach out to realms in the same region as they are deployed"?

smritikjaggi · 2025-03-19T05:42:26Z

app/konnect/regional-consumers.md

@@ -0,0 +1,78 @@
+---
+title: Regional Consumers


Our official name for this initiative is "Consumers". What is the best way for us to reflect that this initiative is an expansion of the existing consumer entity such that consumers can be stored in a centralized space per region?

In my revision, I'll call them "centralized consumer management" or "centrally managed consumers" if I need to call out the difference between them and "original" consumers. Otherwise, I'll use "consumers" when the context makes it clear we're talking about the central ones.

smritikjaggi · 2025-03-19T05:51:27Z

app/konnect/regional-consumers.md

+   * `$CONSUMER_GROUP`: (Optional) Replace with the name of the consumer groups you want to associate with the consumer. Consumer groups set here are additive. This means that if you configure the realm with consumer groups A and B, and then configure the regional consumer with consumer group C, the authenticated consumer will be assigned to consumer groups A, B, and C.
+1. Consumers require authentication. Configure authentication using the [Key Auth plugin](/hub/kong-inc/key-auth/how-to/).
+
+   The order in which you configure the `identity_realms` dictates the priority in which the data plane attempts to authenticate the provided API keys:


We can also list out that the default is scope:cp for Key Auth plugin.

Signed-off-by: Diana <[email protected]>

smritikjaggi

LGTM! Left some comments

app/konnect/centralized-consumer-management.md

smritikjaggi · 2025-03-20T06:58:05Z

app/konnect/centralized-consumer-management.md

+   Save the ID of the realm.
+
+   Be sure to replace the following with your own values:
+   * `{region}`: Region for your {{site.konnect_short_name}} instance.


Today DPs can only reach out to the realms defined in the same region as the DP. Should we add this info somewhere?

yep, I can add that somewhere!

smritikjaggi · 2025-03-20T06:58:44Z

app/konnect/centralized-consumer-management.md

+{:.important}
+> Centralized consumer management is only available for {{site.base_gateway}} 3.10 data planes. Make sure your control plane uses 3.10 data planes at minimum when configuring these consumers.
+
+1. Use the `/realms` endpoint to create a realm and optionally associate it with allowed control planes and time-to-live values:


We define time-to-live further down the document. Should we define it here as well?

I'll leave this one as-is since we typically follow this format in docs where we explain it later in the bullets and it could bloat the step instruction if I put it here.

smritikjaggi · 2025-03-20T09:45:19Z

app/konnect/centralized-consumer-management.md

+
+{:.note}
+> **Note:** If you are using KIC to manage your data plane nodes in {{site.konnect_short_name}}, ensure that you configure the `telemetry_endpoint` in the data plane. You can find the `telemetry_endpoint` in the {{site.konnect_short_name}} UI in [Gateway Manager](https://cloud.konghq.com/gateway-manager/) in the data plane node instructions.
+


Do we want to add a section around changing the scope of consumers from cp to realm? The user will need to do the following call:

POST https://us.api.konghq.com/identity/pools/%7BpoolID%7D/consumers)/Alice-123/keys
{
"type": "legacy" // Migrating Alice's existing keys
"secret": "Alice-api-key"
}

Since that's optional, I'd rather link them to the API spec so they can see what else they can do. Do you have a predicted link to the public API spec?

I am adding a new step to create new keys for the consumer, since I think that was missing.

Co-authored-by: smritikjaggi <[email protected]>

Signed-off-by: Diana <[email protected]>

feat: add support for externalized consumers

807eba5

jschmid1 added the do not merge Issues/ PRs whose changes should not be merged at this time label Jul 18, 2024

Guaris added the review:general Review for general accuracy and presentation. Does the doc work? Does it output correctly? label Jul 22, 2024

Guaris requested a review from lena-larionova July 22, 2024 16:12

lena-larionova added this to the Gateway 3.8 milestone Jul 23, 2024

Guaris self-assigned this Aug 19, 2024

Merge branch 'main' into feat/externalized-consumers

9bddade

Guaris marked this pull request as ready for review August 19, 2024 16:29

Guaris requested a review from a team as a code owner August 19, 2024 16:29

mheap reviewed Aug 19, 2024

View reviewed changes

Guaris reviewed Aug 19, 2024

View reviewed changes

Guaris added 2 commits August 19, 2024 14:19

start restructuring information on this page

a89ecfc

split out pool info into its own doc

ac821af

smritikjaggi reviewed Sep 9, 2024

View reviewed changes

lena-larionova removed this from the Gateway 3.8 milestone Sep 10, 2024

smritikjaggi and others added 4 commits March 6, 2025 11:49

Update _index.md

88a0f59

Testing edit function

Update _index.md

1541c89

Updated the terminology used for realms and the yaml file examples

Merge branch 'main' into feat/externalized-consumers

b99c61a

Draft Konnect centralized consumers page, make edits to key auth plug…

1ffe95c

…in to add realms section Signed-off-by: Diana <[email protected]>

cloudjumpercat added 2 commits March 13, 2025 09:36

Fix endpoints

6a32148

Signed-off-by: Diana <[email protected]>

Finish draft

935f4f9

Signed-off-by: Diana <[email protected]>

cloudjumpercat added the ci:manual-approve:link-validation label Mar 13, 2025

Add notes about replacing values from examples

327dedf

Signed-off-by: Diana <[email protected]>

lena-larionova requested changes Mar 13, 2025

View reviewed changes

lena-larionova reviewed Mar 13, 2025

View reviewed changes

app/konnect/centralized-consumers.md Outdated Show resolved Hide resolved

mheap reviewed Mar 14, 2025

View reviewed changes

cloudjumpercat and others added 2 commits March 14, 2025 10:00

Apply suggestions from code review

05cdcd6

Co-authored-by: lena-larionova <[email protected]>

Apply additional fixes

84b58f3

Signed-off-by: Diana <[email protected]>

cloudjumpercat assigned cloudjumpercat and unassigned Guaris Mar 14, 2025

cloudjumpercat added this to the Gateway 3.10 milestone Mar 14, 2025

cloudjumpercat added ci:manual-approve:link-validation and removed ci:manual-approve:link-validation labels Mar 14, 2025

Fix one link and appease vale

73eab09

Signed-off-by: Diana <[email protected]>

cloudjumpercat reviewed Mar 14, 2025

View reviewed changes

app/_hub/kong-inc/key-auth/how-to/_index.md Outdated Show resolved Hide resolved

appease vale

bbc2109

smritikjaggi reviewed Mar 19, 2025

View reviewed changes

Change consumer wording, remove caps for certain entities

ff589df

Signed-off-by: Diana <[email protected]>

smritikjaggi reviewed Mar 20, 2025

View reviewed changes

cloudjumpercat and others added 2 commits March 20, 2025 08:51

Apply suggestions from code review

d265e99

Co-authored-by: smritikjaggi <[email protected]>

Add info about dps reaching out to realms, add new key step

a3f84e0

Signed-off-by: Diana <[email protected]>


		-- Dummy/Link that points to Konnect Docs when ready.

		With the `pool_id` you obtained from the previous step, you can configure the key-auth plugin to validate API keys against the Identity Service.

		---


		With `pool_id` you can configure the key-auth plugin to validate API keys against the Identity Service.


		With `pool_id` you can configure the key-auth plugin to validate API keys against the Identity Service.

		### Configuring Multiple Pools


		### Configuring Multiple Pools

		In the key-auth plugin configuration, add the `pools` option as shown below:


		In this configuration, the dataplane will initially check the local pool (LMDB) before querying the remote Identity Service.

		If a matching key is found in any of these pools, the request will be authenticated. If the key is not found in any of the configured pools, the request will be blocked.


		If a matching key is found in any of these pools, the request will be authenticated. If the key is not found in any of the configured pools, the request will be blocked.

		### Configuring Single Pools


		### Configuring Single Pools

		It is also possible to configure only a single pool, either local or remote. However, only one of each type can be configured.


		It is also possible to configure only a single pool, either local or remote. However, only one of each type can be configured.

		To configure only a remote pool:


		The following diagram shows how you can configure centralized Consumers in realms as well as scope Consumers to a Control Plane:

		<!--vale off -->

		* Realm isn't associated with a control plane: You can also configure a single `identity_realms` by omitting the `scope: cp` from the example. In this case, the dataplane will only attempt to authenticate API keys against the realm. If the API key isn't found, the request will be blocked.
		* Realm is only associated with a Control Plane: You can configure a look up only in the control plane config by only specifying `scope: cp` for `identity_realms`. In this scenario, the dataplane will only check the control plane configuration (LMDB) for API key authentication. If the API key isn't found, the request will be blocked.


		{:.note}
		> Note: If you are using KIC to manage your data plane nodes in {{site.konnect_short_name}}, ensure that you configure the `telemetry_endpoint` in the data plane. You can find the `telemetry_endpoint` in the {{site.konnect_short_name}} UI in [Gateway Manager](https://cloud.konghq.com/gateway-manager/) in the data plane node instructions.

feat: add support for externalized consumers #7657

Are you sure you want to change the base?

feat: add support for externalized consumers #7657

Conversation

jschmid1 commented Jul 18, 2024 • edited by cloudjumpercat Loading

Description

Testing instructions

Checklist

netlify bot commented Jul 18, 2024 • edited Loading

✅ Deploy Preview for kongdocs ready!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smritikjaggi left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cloudjumpercat commented Mar 11, 2025 • edited Loading

cloudjumpercat commented Mar 13, 2025

cloudjumpercat commented Mar 13, 2025

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smritikjaggi left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

smritikjaggi left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jschmid1 commented Jul 18, 2024 •

edited by cloudjumpercat

Loading

netlify bot commented Jul 18, 2024 •

edited

Loading

cloudjumpercat commented Mar 11, 2025 •

edited

Loading