[EXTDAM-369] Add a filter capability on the s3 bucket Created: 03/Mar/23  Updated: 19/Jul/23  Resolved: 15/Jun/23

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: 1.1.4

Type: Improvement Priority: Neutral
Reporter: Andrei Ichimescu Assignee: Laura Podkoritnik
Resolution: Fixed Votes: 0
Labels: cs-bk
Remaining Estimate: 0d
Time Spent: 4.5h
Original Estimate: Not Specified

Attachments: PNG File example.png    
Issue Links:
Cloners
is cloned by EXTDAM-390 Port to Master - Add a filter capabil... Closed
Relates
dependency
is depended upon by EXTDAM-386 Release EXTDAM 1.1.4 Closed
relation
is related to EXTDAM-388 DOCU: S3 bucket prefixes Closed
supersession
supersedes EXTDAM-225 [S3] Ability to set the rootPath to a... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[X]  Architecture Decision Record (ADR)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: AuthorX Support
Story Points: 3
Team: AuthorX
Work Started:
Approved:
Yes

 Description   

Currently we are using a whitelist mechanism to only select the target buckets for the external dam.

Some customers can only use a single bucket for multiple purposes (dev, staging, prod environment) and they require that the s3 items to be isolated based on a prefix key

 

We need to enhance this filter by providing a "prefix" key for the S3Items.
 

Acceptance criteria

 * create a new config key for the external dam.
 * Filter the data retrieved from aws s3 by this key.
 * make sure that the dialog choosers take into consideration the filtering:

 


Generated at Mon Feb 12 01:54:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.