skoruba/IdentityServer4.Admin

Redesign seeding of database

Open

#502 opened on Feb 16, 2020

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

Description

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. 👍🏼

Contributor guide

Tech stack
csharpsql
Domain
backenddatabase
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C#ASP.NET CoreEntity Framework CoreIdentityServer4
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
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.