[MGNLGQL-104] GraphQL can query assets - also when dam-jcr module is not installed Created: 01/Sep/21 Updated: 25/Mar/22 |
|
| Status: | Open |
| Project: | Magnolia GraphQL |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
[ ]*
asset CT property type is available in SaaS environment and provides linking to S3 assets
[ ]*
assets can be used in GraphQL
[ ]*
assets can be linked and expanded in delivery endpoints
|
||||||||
| 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)
|
||||||||
| Epic Link: | External DAM MVP | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
GraphQL module's DAM support is dependent on dam-jcr (and even brings in some decoration of asset CT). Since in SaaS we rely solely on external assets coming from S3/Fastly, an alternative solution needs to be proposed. Note: GraphQL Queries allow specifying the asset provider - such as jcr or s3. The default provider is jcr. Also consider if we want to have a differentr default provider on SaaS - S3.
|