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

Chi-Hsuan Huang commented on HDDS-15583:
----------------------------------------

I'd like to help with this. I looked into it a bit and wanted to share a 
possible plan.

It seems to split naturally into three pieces:

1. *Install awscli v2 (pinned) in ozone-docker-runner:* separate repo, ideally 
lands first so CI can use v2. Similar to HDDS-12499.
2. {*}Switch the S3 smoketests to v2{*}: in this repo. Most `aws` calls go 
through {_}s3/commonawslib.robot{_}, so it's fairly concentrated. Mainly 
updating the install/setup and handling v2 differences (output pager, checksum 
defaults).
3. {*}Remove awscli v1{*}: later, after July 2027.

One note: the old v2 `cp`/`mv` MPU blocker (HDDS-7992) came from the `?tagging` 
pre-request, which should now be obsolete since tagging is supported (and 
HDDS-12488/HDDS-12123 handle the v2 checksum trailer). I'd confirm by getting 
`MultipartUpload.robot` green under v2.

Does splitting it this way make sense? 

> Upgrade to awscli v2
> --------------------
>
>                 Key: HDDS-15583
>                 URL: https://issues.apache.org/jira/browse/HDDS-15583
>             Project: Apache Ozone
>          Issue Type: Task
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>
> The aws cli v1 is entering maintenance mode soon in July 2026, and end of 
> support July 2027. 
> https://aws.amazon.com/blogs/developer/cli-v1-maintenance-mode-announcement/
> The latest version is 1.45.30 https://pypi.org/project/awscli/
> We should add aws v2 in the ozone [docker 
> runner|https://github.com/apache/ozone-docker-runner/blob/558b2caaed37dd34aad1c17aa68b3d63715543d6/Dockerfile#L80],
>  update scripts to exercise aws v2 commands. And then remove aws v1 some 
> point after July 2027.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to