skoruba/IdentityServer4.Admin

Redesign seeding of database

Open

#502 opened on 2020年2月16日

GitHub で見る
 (2 comments) (0 reactions) (1 assignee)C# (3,486 stars) (1,125 forks)batch import
help wantedpriority: mediumtask

説明

For some use case is necessary to be able choose which db context is required for migration and seeding as well.

I am wondering about these modifications:

  • Add some parameters into AppSettings.json:
    • RunSeed
    • RunMigrationIdentityServerConfiguration -RunMigrationIdentityServerPersistedGrants
    • RunMigrationIdentity
    • RunMigrationAuditLogging
    • RunMigrationLogging

Final tables will be created according to options above.

Another thing is that maybe it would be fine - move whole process of seeding and database migration to separate project which it will be responsible only for this part.

Feedback is welcome. 👍🏼

コントリビューターガイド

技術スタック
csharpsql
領域
backenddatabase
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
blocked
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
needs investigation
前提条件
C#ASP.NET CoreEntity Framework CoreIdentityServer4
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
15
調査方針
The issue proposes adding configuration options to AppSettings.json to control which database contexts are migrated/seeded, and possibly moving migration and seeding logic to a separate project. To proceed, look at the existing migration and seeding code in the repository (e.g., Data/Migrations and Data/Seed folders). Check the linked PRs (none) and comments to see if maintainers have clarified their acceptance criteria. The assignee may provide guidance; otherwise, ask maintainers about preferred approach and scope before implementing.