[HASSETS-6] Can't create hybrid asset by linking Created: 01/Sep/20 Updated: 17/Sep/20 Resolved: 17/Sep/20 |
|
| Status: | Closed |
| Project: | Hybrid Assets |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Andrew Warinner | Assignee: | Andrew Warinner |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
Creating a hybrid asset with the "Link external content" actions in the DAM app fails with "Invalid content" error. Extract from log: INFO info.magnolia.dam.hybrid.store.S3AssetStore 28.08.2020 08:32:42 – Could not get region for bucket s3magnolia: The AWS Access Key Id you provided does not exist in our rec
It appears the content store configuration referenced provider (/modules/dam/config/providers/jcrProvider/stores@extends) does not pick up the store configuration, perhaps due a module load order problem. Note: not reproducible! Does not occur in a local development environment and went away after restarting the test container in Docker! |
| Comments |
| Comment by Andrew Warinner [ 17/Sep/20 ] |
|
Fixed in v1.0.1. |