Allow multiple signatures to be defined in your configuration file about aspnetcore-extensions HOT 5 CLOSED

Wouldn't this better be solved by using multiple per-env configs?

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-3.1

from aspnetcore-extensions.

Yeah, that is the other way of doing it. It's just that we would have a lot of extra configurations and each load balanced node would need their own configuration. This would also mean a configuration for each developer for their own local webhook...

from aspnetcore-extensions.

Currently this is the only setting that would necessitate all these extra environment configurations in our current project,.. I'd be more inclined to keep the signature handler we have instead of using the new one to avoid all these extra environment configs.

from aspnetcore-extensions.

Thanks for the explanation!

I understand your arguments but it is the best practice to do it that way. That's exactly what the env-configs are meant for. If it's easier for you to do it differently then go ahead but I don't think it's a good idea to include the aforementioned functionality in this package. Therefore, I'd close the issue now.

If you disagree, feel free to reopen this issue and add more comments.

from aspnetcore-extensions.

Sounds good, thanks for taking a look.

from aspnetcore-extensions.