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.

Sign up for GitHub

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

Jump to bottom

Stream aliases #59

Closed
sshaikh opened this issue Aug 17, 2020 · 5 comments
Closed

Stream aliases #59

sshaikh opened this issue Aug 17, 2020 · 5 comments
Labels
enhancement New feature or request

Comments

@sshaikh
Copy link

sshaikh commented Aug 17, 2020

Which version are you using?

v0.9.10

Describe the problem

It might be useful to provide alternative paths for the same stream, without creating a new entry in the config (depending on the implementation this may save some memory/cpu too).
@aler9 aler9 added the enhancement New feature or request label Aug 17, 2020
@aler9
Copy link
Member

aler9 commented Aug 17, 2020 •
edited
Loading

Hello, there is a pending PR that implements wildcard paths; i'm waiting for the author to do some changes, otherwise after a while i'll implement the feature myself.
Regexp paths would make aliases possible, for instance the path "path1|path2" would match both path1 and path2.

aler9 added a commit that referenced this issue Sep 19, 2020
@aler9
implement paths with regular expressions (#54) (#59)
6679b02
@aler9
Copy link
Member

aler9 commented Sep 19, 2020

Paths with regular expressions have been implemented into master; this does not allow stream aliases but allows to share a configuration between two paths.

@sshaikh
Copy link
Author

sshaikh commented Sep 19, 2020

Good enough! The main concern was to not duplicate the processing on the backend so regexps work.

@aler9
Copy link
Member

aler9 commented Oct 6, 2020

added in v0.10.0

@aler9 aler9 closed this as completed Oct 6, 2020
@github-actions
Copy link
Contributor

github-actions bot commented Jan 1, 2023

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sshaikh @aler9