Include Idempotent scripts for each release

[DaleyKD]

To continue on the ideas of #55 , I was able to get this to work with my existing local IdS setup. I plugged a reference to the docker image into my docker-compose and added a bunch of necessary overrides to get it working.

The biggest downfall for me was that the /seed switch wants to seed all 5 DbContexts, when in reality, I only need 2 or 3. I don't want it to try and seed my IdS tables; they already exist.

Therefore, I used Script-Migration -Idempotent for the 3 DbContexts I needed. I'll also create a seed SQL script to insert a necessary Client into the IdS database, and to populate the Roles / Users of the Identity tables.

My main fear is what future upgrades will look like when it comes to migration. If you include an Idempotent script for each of them, then maybe I won't have to pull the source down, and generate my own scripts for every release.

I'm open to better ideas for running this alongside an existing IdS server (I do not want this to run as an Area or whatever in my IdS server).

The best goal is to give it the docker overrides it needs and it just works. Manually running SQL scripts is a pain.

[skoruba]

Thanks for your feedback, I will think about this use case. Do you use asp.net core identity?

[DaleyKD]

I appreciate the consideration.

We don't use Asp.Net Core Identity with IdS, but using it with IdentityServer4.Admin would not be a huge issue. Obviously, I'd prefer to NOT use it, but that's not a deal breaker.

My eventual goal would be to just "spin this up" in Azure so that we can access it privately (not exposed to the public) to help with a few minor administration tasks. Doing that with minimal manual steps would be superb.