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.
Redesign seeding of database · skoruba/IdentityServer4.Admin#502 | Good First Issue