Skip to content
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

config: allow multiple -inline-routes value #3383

Closed
wants to merge 1 commit into from

Conversation

AlexanderYastrebov
Copy link
Member

Extend config.Config and skipper.Options to allow multiple sets of routes in eskip format for convenience.

Fixes #3366

@AlexanderYastrebov AlexanderYastrebov added the major moderate risk, for example new API, small filter changes that have no risk like refactoring or logs label Jan 23, 2025
@AlexanderYastrebov AlexanderYastrebov marked this pull request as ready for review January 23, 2025 15:01
Extend config.Config and skipper.Options to allow multiple sets
of routes in eskip format for convenience.

Fixes #3366

Signed-off-by: Alexander Yastrebov <[email protected]>
@AlexanderYastrebov AlexanderYastrebov marked this pull request as draft January 24, 2025 08:30
@@ -125,7 +125,7 @@ type Config struct {
EtcdPassword string `yaml:"etcd-password"`
RoutesFile string `yaml:"routes-file"`
RoutesURLs *listFlag `yaml:"routes-urls"`
InlineRoutes string `yaml:"inline-routes"`
InlineRoutes multiFlag `yaml:"inline-routes"`
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a breaking change for yaml-based configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major moderate risk, for example new API, small filter changes that have no risk like refactoring or logs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support multiple values for -inline-routes flag
1 participant