-
Notifications
You must be signed in to change notification settings - Fork 1
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
Gateway entities: services, consumers, plugins, consumer groups #172
Conversation
✅ Deploy Preview for kongdeveloper ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
where is this happening? we need to apply the liquify filter to it, i.e.
We have the following styles for admonitions
I fixed it on your branch :) |
f69a8af
to
d24d1c2
Compare
To start creating your own plugins, review the Getting Started documentation, or see the following references: | ||
|
||
* Plugin Development Kit reference | ||
* Other Language Support | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Links TBA, we don't have these pages yet, and the first one is meant to be generated.
|
||
## What is a Consumer Group? | ||
|
||
Consumer Groups enable the organization and categorization of [Consumers](/gateway/entities/consumer/) (users or applications) within an API ecosystem. By grouping Consumers together, you eliminate the need to manage them individually, providing a scalable, efficient approach to managing configurations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I liked the call out you had on Consumers about them not always being "human", could we add some wording like that to here as well?
- q: What is the difference between Consumers and Applications? | ||
a: | | ||
Applications provide developers the ability to get access to APIs managed by {{site.base_gateway}} or Konnect | ||
with no interaction from the Kong admin team to generate credentials required. | ||
Applications provide developers the ability to get access to APIs managed by {{site.base_gateway}} or {{site.konnect_short_name}} | ||
with no interaction from the Kong admin team to generate the required credentials. | ||
<br><br> | ||
With consumers, the Kong team creates consumers, generates credentials and needs to share them with the developers that need access to the APIs. | ||
You can think as applications as a type of consumer in Kong that allows developers to automatically obtain credentials for and subscribe to the required APIs. | ||
With Consumers, the Kong team creates Consumers, generates credentials, and shares them with the developers that need access to the APIs. | ||
You can think of Applications as a type of Consumer in Kong that allows developers to automatically obtain credentials for, and subscribe to the required APIs. | ||
|
||
- q: What is the difference between consumers and developers? | ||
- q: What is the difference between Consumers and Developers? | ||
a: | | ||
Developers are real users of the Dev Portal, whereas consumers are abstractions. | ||
Developers are real users of the Dev Portal, whereas Consumers are abstractions. | ||
|
||
- q: What is the difference between consumers and RBAC users? | ||
- q: What is the difference between Consumers and RBAC Users? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Application, Developers, and RBAC Users capitalization threw me here a bit. I guess they are entities, but they feel less like a core entity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I think we have to leave them like this for consistency. Otherwise we'll start arbitrarily drawing the line between what is "core" and what isn't, which isn't actually a set definition.
app/_gateway_entities/plugin.md
Outdated
@@ -42,6 +43,73 @@ The set of plugins you have access to depends on your license tier. | |||
|
|||
You can also develop custom plugins, adding your own custom functionality to {{site.base_gateway}}. | |||
|
|||
## Plugin precedence |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd move this section to plugin scopes. I had questions about precedence while I was reading it and this is more detailed reference material than the intro/overview content that's on the entity pages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, i like this idea. I struggled with keeping precedence info as a separate page, but if it goes with scopes, it fits more naturally.
@@ -42,6 +43,73 @@ The set of plugins you have access to depends on your license tier. | |||
|
|||
You can also develop custom plugins, adding your own custom functionality to {{site.base_gateway}}. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I can think of that might be nice to add here is a small list of the main plugin "themes" Kong has, just to give an idea what a plugin can do. Like:
- Traffic control
- Authentication
- AI
- etc.
Co-authored-by: Diana <[email protected]>
Preview Links
Updating entities that already have pages:
And adding a new page for Consumer Groups.
To do:
https://deploy-preview-172--kongdeveloper.netlify.app/gateway/entities/consumer-group/
https://deploy-preview-172--kongdeveloper.netlify.app/gateway/entities/consumer/
https://deploy-preview-172--kongdeveloper.netlify.app/gateway/entities/service/
https://deploy-preview-172--kongdeveloper.netlify.app/gateway/entities/plugin/
Notes and questions
{{ variable.name}}
doesn't seem to work in yaml consistentlyNotes styling: it's fine that it doesn't exist yet, but is there a format that we should follow that'll eventually get styled?Something weird going on with arrows in mermaid: https://deploy-preview-172--kongdeveloper.netlify.app/gateway/entities/consumer-group/Is it possible to generate https://deploy-preview-172--kongdeveloper.netlify.app/plugins/scopes/ now, and can we (authors) write these generators, if possible?Checklist