skoruba/IdentityServer4.Admin

Redesign seeding of database

Open

#502 opened on Feb 16, 2020

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

Repository metrics

Stars
 (3,486 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Investigate the current seeding and migration code in the repository. Understand how DbContext instances are configured and used. Evaluate the proposed AppSettings parameters and consider if separate project would simplify maintenance. Look for existing patterns in similar projects.
Tech stack
csharp
Domain
backenddatabase
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C#Entity FrameworkIdentityServer4
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50