Feature: Can we have distributed configuration for each services?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 70
- Forks
- 15
- Avg merge
- 1h 58m
- Merged PRs (30d)
- 42
Description
Description
Hi team,
First of all, thank you for building this great tool — it's very helpful for GitOps workflows with APISIX.
❓ Problem
Currently, adc.yaml stores all configurations (services, routes, upstream, etc.) in a single YAML file. As the system scales with many services and teams, maintaining a monolithic file becomes hard to manage, review, and track changes.
🚀 Feature Request
Please support loading adc.yaml configuration from multiple files, structured by service or resource type. For example:
adc/
├── services/
│ ├── mockbin.yaml (having routes and import upstream in this file)
│ └── httpbin.yaml (having routes and import upstream in this file)
├── upstream/
│ ├── jane.yaml
│ └── john.yaml
Thank you so much !!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the existing adc.yaml configuration is loaded, then compare that path with the proposed adc/services and adc/upstream layout. The work is complete when configurations can be split across multiple files by service or resource type, including routes and imported upstreams as described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100