Submodule Contents Not Included in Releases

[z-tejani]

Describe the bug

Issue can be found in the packaged (tar) releases found here: https://github.com/aws/aws-sdk-cpp/tags

Navigating to aws-sdk-cpp/crt/aws-crt-cpp will yield a blank folder. The contents of the submodule are not included in the relase artifact. Similarly, in the submodule repo "aws-crt-cpp" releases (found here: https://github.com/awslabs/aws-crt-cpp/tags) navigating to the crt directory will yield all of the submodules as blank directories rather than pulling their contents.

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Submodule contents should be yielded in parent release.

Current Behavior

Submodules yield blank directories in their place.

Reproduction Steps

Download the release artifact, navigate to crt directory.

Possible Solution

No response

Additional Information/Context

No response

AWS CPP SDK version used

1.11.698

Compiler and Version used

global

Operating System and version

RHEL 9.6

[sbiscigl]

This is intentional and explained in a previous versions readme

Alternatively, if you downloaded the code bundle from GitHub website and have no installation of git, you can download all the dependencies running the prefetch_crt_dependency.sh script from the root of the repository. It will download bundles of all dependencies from github website using curl and expand them in the right locations.

so in a dockerfile this would look like

FROM public.ecr.aws/amazonlinux/amazonlinux:2023
RUN yum groupinstall "Development Tools" -y
RUN yum install -y jq curl-devel openssl-devel ninja-build cmake3

RUN curl -L -o aws-sdk-cpp.tar.gz https://github.com/aws/aws-sdk-cpp/archive/refs/tags/1.11.700.tar.gz &&\
    tar -xzf aws-sdk-cpp.tar.gz &&\
    cd aws-sdk-cpp-1.11.700 &&\
    ./prefetch_crt_dependency.sh &&\
    mkdir build &&\
    cd build &&\
    cmake -GNinja -DBUILD_ONLY="s3" -DAUTORUN_UNIT_TESTS=OFF .. &&\
    cmake --build .

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.