You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I am using the Command Center to execute any migration script, it always fails.
To Reproduce
Steps to reproduce the behavior:
Create a new migration via the 'dotnet ef migrations add ' command.
Start the server and open the Command Center.
Go to your database model
Select the created migration under the migration tab.
Click "apply selected migration"
Expected behavior
The migration is applied and removed from the list.
Environment:
Moryx.CommandCenter.Web Version 6.2.5
Additional context
Initial investigations using the developer console have shown that the endpoint addressed by the command center does not exist.
The Command Center requests the URL http://<hostname>/databases/<database-model>/<migration-script>/migrate via a post request which results in a 404 Not Found.
Workaround:
Call the endpoint without the name of the migration script by using Postman or curl. But be careful it executes all available migrations related to the provided model.
URL:
Describe the bug
When I am using the Command Center to execute any migration script, it always fails.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The migration is applied and removed from the list.
Environment:
Additional context
Initial investigations using the developer console have shown that the endpoint addressed by the command center does not exist.
The Command Center requests the URL
http://<hostname>/databases/<database-model>/<migration-script>/migrate
via a post request which results in a 404 Not Found.Workaround:
Call the endpoint without the name of the migration script by using Postman or curl. But be careful it executes all available migrations related to the provided model.
URL:
Request Body:
The text was updated successfully, but these errors were encountered: