[jira] [Commented] (HDDS-6608) [MultiTenancy] Create uniform output for AWS secrets across APIs

["Siyao Meng (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533953#comment-17533953 ] 

Siyao Meng commented on HDDS-6608:
----------------------------------

In the second case, at the moment, the {{-e}} argument would need to be added to get the export format, as the {{getsecret}} subcommand here is inherited from {{ozone s3 getsecret}}.

Yes it is a good idea to make it consistent.

> [MultiTenancy] Create uniform output for AWS secrets across APIs
> ----------------------------------------------------------------
>
>                 Key: HDDS-6608
>                 URL: https://issues.apache.org/jira/browse/HDDS-6608
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone CLI
>    Affects Versions: 1.3.0
>            Reporter: Soumitra Sulav
>            Priority: Minor
>              Labels: ozone-multitenancy
>
> While assigning user to tenant, it logs the access/secret key on the console in shell export variables.
> {code:java}
> bash-4.2$ ozone tenant user assign '**' -t tenantone
> Assigned '**' to 'tenantone' with accessId 'tenantone$**'.
> export AWS_ACCESS_KEY_ID='tenantone$**'
> export AWS_SECRET_ACCESS_KEY='35d5075f8a4d5dce4a6491a06c2f6f7cf4c2ba443f7f483841551d923527ebcf'{code}
> But while fetching the keys via getsecret API the output is in different format.
> {code:java}
> bash-4.2$ ozone tenant user getsecret 'tenantone$**'
> awsAccessKey=tenantone$**
> awsSecret=35d5075f8a4d5dce4a6491a06c2f6f7cf4c2ba443f7f483841551d923527ebcf {code}
> Better to have similar format. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org