-
Notifications
You must be signed in to change notification settings - Fork 37
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
[Enhancement][nightly playground] custom the changes #150
Comments
Hi @Flyingliuhub @seraphjiang , Thank you for creating the request.
There are 2 ways we can proceed with this request.
We can add as many custom feature flags as we want. However, just to make things clear at this point we intend to only have 2 endpoints, one point to upcoming 2.x release and other one point to next major version which is 3.0.0 cc: @bbarani @rishabh6788 |
Closing this issue. Please see README for other FAQs. |
Is your feature request related to a problem? Please describe.
The latest version of Playground Nightly has been released. We would like to add some requirements to meet our current needs.
Describe the solution you'd like
The tarball can be built from any repo and any branch, which is currently required by a lot of teams for purposes such as demonstration, bug fixes, and quickly previewing the new changes. For example, the PR raised by internal team or external users may use a different repo and branch than the current one, and we need to build a tarball for cross-team feature work, which requires all the different repos/branches from each developer.
We would like to seed data (multiple data sources) into the nightly playground as well.
All other team need the custom feature flag as well.
All other teams' seed data, such as observability, alerts, security analytics, reporting, anomaly detection, etc.
Describe alternatives you've considered
N/A
Additional context
N/A
cc: @seraphjiang
The text was updated successfully, but these errors were encountered: