-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Media.AmazonS3 requires AccessKeyId if NuGet package is used #12570
Comments
/cc @neglectedvalue |
Hello seems like the issue is in configuration files in decoupled mode, I was able to reproduce this bug with AWS and Azure modules.
Upd: |
@jtkech your though? |
I guess it does use the appsettings.json from the project, but only partially because the media provider itself is recognized during the bootstrap process. |
What do you mean by media provider itself? If you are talking about S3/Azure media storages - they are using appsettings only to get storage configuration, their bootstrap happens only if you are enabled them in admin->features or created a custom recipe. |
I remember the configuration could came from different sources, but there should be an order and fallback in case one of the configuration provider is missing |
Yes, sorry my bad. Off course you're right 🤦🏽♂️ |
Is this a general bug then, that in decoupled mode using the NuGet packages, the appsettings.json hierarchy is not respected? |
Decoupled (not front-end theme, no layout shapes) should have nothing to do with appsettings. Maybe you could debug the source to understand where this makes a difference. |
If you reference |
Closing due to no reply from the author. |
@Piedone, I didn't answer because I thought it's out of my hand. Since @neglectedvalue was able to reproduce it:
@hishamco and @jtkech should probably decide what the correct behavior should be. |
Please follow up from here: #12570 (comment) JT, sadly, won't help anymore: #14954. |
My condolences 🫶 In my opinion, the correct behavior should be as follows:
If a setting is present in both appsettings.json files, the more specific |
That's what indeed should happen. What you see is I think less related to NuGet, and should more lie in how the app is initialized (and thus how it loads configuration). Can you share your Program.cs and compare it with the one in OC's |
Describe the bug
I'm experiencing a very strange behaviour. I'm implementing the OrchardCore.Media.AmazonS3 storage provider. If I clone the OrchardCore repository and create a config entry like this:
everthing seems to work just fine.
If I however create a new decoupledCMS project and add a plain MVC Project and add just the following NuGet packages
I get the following error message:
Eventhough I use the exact same config as mentioned obove, any ideas what I might missing?
The text was updated successfully, but these errors were encountered: