skoruba/IdentityServer4.Admin

Redesign seeding of database

Open

#502 建立於 2020年2月16日

在 GitHub 查看
 (2 留言) (0 反應) (1 負責人)C# (3,486 star) (1,125 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.