You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/04/24 13:58:00 UTC
[jira] [Resolved] (HADOOP-16252) Use configurable dynamo table name
prefix in S3Guard tests
[ https://issues.apache.org/jira/browse/HADOOP-16252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-16252.
-------------------------------------
Resolution: Fixed
Assignee: Ben Roling
Fix Version/s: 3.3.0
+1, committed to trunk. Thanks!
> Use configurable dynamo table name prefix in S3Guard tests
> ----------------------------------------------------------
>
> Key: HADOOP-16252
> URL: https://issues.apache.org/jira/browse/HADOOP-16252
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Ben Roling
> Assignee: Ben Roling
> Priority: Major
> Fix For: 3.3.0
>
>
> Table names are hardcoded into tests for S3Guard with DynamoDB. This makes it awkward to set up a least-privilege type AWS IAM user or role that can successfully execute the full test suite. You either have to know all the specific hardcoded table names and give the user Dynamo read/write access to those by name or just give blanket read/write access to all Dynamo tables in the account.
> I propose the tests use a configuration property to specify a prefix for the table names used. Then the full test suite can be run by a user that is given read/write access to all tables with names starting with the configured prefix.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org