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
v6 plans #4380
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
unleash/src/lib/middleware/rbac-middleware.ts Lines 73 to 92 in 9683dda
|
Removing |
docs on upgrading from v5 to v6, changes needed, breaking things, etc. |
Should we consider consolidating all migration files into a single file? We have 276 migrations. We could do a fresh DB dump after all migrations to start fresh |
What would be the gain? (Assume positive intentions, I'm curious, I'm not trying to be negative here) |
If I'm reading the original comment correctly, we'd squash all the migrations into a single SQL script which would give us the opportunity to avoid some of those dangerous migrations that need to be done in phases I do agree though, this sounds like it'd cause more pain than happiness |
Asking the right questions! I was looking for performance gains. Gathering some data... In my local machine.
This also impacts on test execution speed. I ran Test Suites: 2 failed, 301 passed, 303 total
Tests: 2 failed, 2 skipped, 2786 passed, 2790 total
Snapshots: 103 passed, 103 total
Time: 199.772 s, estimated 203 s And I logged up migration times:
The issue is that the dump is not that great for migrations and without taking into account the failures I also didn't see a performance boost: Test Suites: 34 failed, 269 passed, 303 total
Tests: 126 failed, 2 skipped, 2662 passed, 2790 total
Snapshots: 101 passed, 101 total
Time: 190.593 s, estimated 199 s |
Support for in-memory mode would be great. Our use case would be to run the container in short lived isolated scenarios (e.g. integration testing, running apps locally, CI) and not having to also run Postgres as part of this would make the experience "lighter". |
@chriswk I think we need to support at least v13 for another year. We have a few larger enterprises still stuck on that version. |
You can run https://github.com/Unleash/unleash-edge in offline mode to support that use case. |
I would love to see ESM support 🥳 |
Decided:
/edge/metrics
endpointUnder consideration:
id
column in thepermissions
table (this is an internal db change).message
property or thedescription
property but not bothDropped (did not make it for the v6 plans)
Background
A major version is an opportunity to remove deprecated features and add new features to our deprecation list.
The text was updated successfully, but these errors were encountered: