mirror of
https://github.com/pterodactyl/panel.git
synced 2024-11-25 10:32:31 +01:00
Theoretically fix migration issues for api_key table
This commit is contained in:
parent
5f6c153537
commit
d03559080f
@ -9,6 +9,7 @@ This project follows [Semantic Versioning](http://semver.org) guidelines.
|
||||
* Handle 404 errors from missing models in the application API bindings correctly.
|
||||
* Fix validation error returned when no environment variables are passed, even if there are no variables required.
|
||||
* Fix improper permissions on `PATCH /api/servers/<id>/startup` endpoint which was preventing enditing any start variables.
|
||||
* Should fix migration issues from 0.6 when there are more than API key in the database.
|
||||
|
||||
### Changed
|
||||
* Changes order that validation of resource existence occurs in API requests to not try and use a non-existent model when validating data.
|
||||
|
@ -16,7 +16,7 @@ class SetupTableForKeyEncryption extends Migration
|
||||
public function up()
|
||||
{
|
||||
Schema::table('api_keys', function (Blueprint $table) {
|
||||
$table->char('identifier', 16)->unique()->after('user_id');
|
||||
$table->char('identifier', 16)->nullable()->unique()->after('user_id');
|
||||
$table->dropUnique(['token']);
|
||||
});
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user