Issue #2139: switch tarball install flow to CloudFront indexes#4644
Issue #2139: switch tarball install flow to CloudFront indexes#4644rwilliamspbg-ops wants to merge 3 commits intoROCm:mainfrom
Conversation
|
Please format the PR description |
|
Issue #2139 tracks the move away from direct S3 bucket access for release tarballs. Prerelease tarballs are CloudFront-only, so the installer needs to use CloudFront tarball indexes instead of S3 API calls. Technical Details |
Summary\nSwitch release-tarball lookup/download in install_rocm_from_artifacts.py from direct S3 bucket API calls to CloudFront tarball indexes.\n\n## Why\nIssue #2139 tracks that prerelease tarballs are CloudFront-only and should not depend on public S3 bucket access.\n\n## Changes\n- Parse tarball asset names from CloudFront index content\n- Support both anchor href listings and JavaScript "name" file-list format\n- Resolve latest nightly release from CloudFront index\n- Download release tarballs from CloudFront URLs\n- Update release-version help text to CloudFront endpoints\n- Update tarball table in RELEASES.md to prefer CloudFront indexes\n\n## Validation\n- python build_tools/install_rocm_from_artifacts.py --latest-release --amdgpu-family gfx110X-all --dry-run\n- python build_tools/install_rocm_from_artifacts.py --release 6.4.0.dev0+8f6cdfc0d95845f4ca5a46de59d58894972a29a9 --amdgpu-family gfx120X-all --dry-run\n\nCloses #2139