[EXTDAM-390] Port to Master - Add a filter capability on the s3 bucket Created: 19/Jun/23 Updated: 23/Jun/23 Resolved: 23/Jun/23 |
|
| Status: | Closed |
| Project: | External DAMs |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1.4, 1.2.0 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Andrei Ichimescu | Assignee: | Miguel Martinez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | cs-bk | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||||||
| Epic Link: | AuthorX Support | ||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||
| 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.
|