feature: exclusion/inclusion of plugins via additional metadata on services/routes
- Dominant language
- Go
- Stars
- 503
- Forks
- 137
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 20
Description
Users have expressed a need for two things:
- Ability to apply a global plugin but exclude certain services/routes (https://github.com/Kong/kong/issues/5233)
- Ability to define plugins templates and then directly use them on services/routes
The scope here is to figure out a way to define these things using decK's state file and then decK does the heavy lifting in the background to render the correct state and sync it to Kong.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by examining decK's state-file handling and how Kong services, routes, and plugins are represented; done requires a decided metadata design that supports global-plugin exclusions and reusable plugin templates, then renders and syncs the correct Kong state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100