#cloudposse (2024-08)
<http://cloudposse.com/quiz | cloudposse.com/quiz> |
Want to hire Cloud Posse? Take our quiz. <http://cloudposse.com/quiz | cloudposse.com/quiz> |
2024-08-19
any one can support me with this
Hello, team! so i am trying to automate (IAC) our glue services iam-role, s3, Glue Job, Workflow i am facing this error when i use
terraform {
source = "tfr:///cloudposse/s3-bucket/aws?version=2.0.3"
}
to import s3 module or importing iam-role module
terraform {
source = "tfr:///cloudposse/iam-role/aws?version=0.19.0"
}
Error is
'.terraform\modules\s3_user.s3_user'...
│ fatal: '$GIT_DIR' too big
i tried everything possible increased buffer size, downloaded the module manualy and point the source to my local but still no use any help please
This has nothing to do with our modules.
Hello, team! so i am trying to automate (IAC) our glue services iam-role, s3, Glue Job, Workflow i am facing this error when i use
terraform {
source = "tfr:///cloudposse/s3-bucket/aws?version=2.0.3"
}
to import s3 module or importing iam-role module
terraform {
source = "tfr:///cloudposse/iam-role/aws?version=0.19.0"
}
Error is
'.terraform\modules\s3_user.s3_user'...
│ fatal: '$GIT_DIR' too big
i tried everything possible increased buffer size, downloaded the module manualy and point the source to my local but still no use any help please
i am trying to dig in it if you have any advice i would be very thankful
This is related? https://github.com/aws/aws-iot-device-sdk-cpp-v2/issues/157
Confirm by changing [ ] to [x] below to ensure that it’s a bug:
• I’ve searched for previous similar issues and didn’t find any solution
Describe the bug
Git on Windows have characters limits for paths, and the latest dependencies are causing some build artifacts to be ~200 characters long, failing the build if the root directory of the build is close to or over 60 characters. The normally recommended git setting core.longpaths=true
doesn’t resolve the issue.
Platform/OS/Device
Windows 10
SDK version number
v1.8.0
To Reproduce (observed behavior)
With an admin account:
git config --system core.longpaths true
mkdir C:\data\awstemp_1234567890123456789012345678901234567890\sdk-cpp-workspace
pushd C:\data\awstemp_1234567890123456789012345678901234567890\sdk-cpp-workspace
git clone -c core.longpaths=true --recursive <https://github.com/aws/aws-iot-device-sdk-cpp-v2.git>
Logs/output
< ✂ >
Cloning into 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-common/verification/cbmc/aws-templates-for-cbmc-proofs'...
fatal: '$GIT_DIR' too big
fatal: clone of '<https://github.com/awslabs/aws-templates-for-cbmc-proofs.git>' into submodule path 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-common/verification/cbmc/aws-templates-for-cbmc-proofs' failed
Failed to clone 'verification/cbmc/aws-templates-for-cbmc-proofs'. Retry scheduled
Cloning into 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-common/verification/cbmc/aws-templates-for-cbmc-proofs'...
fatal: '$GIT_DIR' too big
fatal: clone of '<https://github.com/awslabs/aws-templates-for-cbmc-proofs.git>' into submodule path 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-common/verification/cbmc/aws-templates-for-cbmc-proofs' failed
Failed to clone 'verification/cbmc/aws-templates-for-cbmc-proofs' a second time, aborting
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-compression': checked out 'f2be13afe410611fcac07b6519b96ce1ad4e4831'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-event-stream': checked out '873f1c035a5b6b4698280ee3798d1db5cc9ce86c'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-http': checked out '98b3e4979fc41f54c13a68475919fa56b5377aef'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-io': checked out '919c27a6c0369c71770cb37f855cea67e81a8d4a'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-mqtt': checked out '199352c90c8a7b38b68e9d285538f32fec774f0d'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-checksums': checked out 'fb96b3e964fe9bde2625c3ac9547e54d6c802211'
Submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n': checked out '1616f313f69c168c141d3e78f34cd1f9da920f3a'
Submodule 'tests/cbmc/aws-templates-for-cbmc-proofs' (<https://github.com/awslabs/aws-templates-for-cbmc-proofs>) registered for path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n/tests/cbmc/aws-templates-for-cbmc-proofs'
Cloning into 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n/tests/cbmc/aws-templates-for-cbmc-proofs'...
fatal: '$GIT_DIR' too big
fatal: clone of '<https://github.com/awslabs/aws-templates-for-cbmc-proofs>' into submodule path 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n/tests/cbmc/aws-templates-for-cbmc-proofs' failed
Failed to clone 'tests/cbmc/aws-templates-for-cbmc-proofs'. Retry scheduled
Cloning into 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n/tests/cbmc/aws-templates-for-cbmc-proofs'...
fatal: '$GIT_DIR' too big
fatal: clone of '<https://github.com/awslabs/aws-templates-for-cbmc-proofs>' into submodule path 'C:/data/awstemp_1234567890123456789012345678901234567890/sdk-cpp-workspace/aws-iot-device-sdk-cpp-v2/aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n/tests/cbmc/aws-templates-for-cbmc-proofs' failed
Failed to clone 'tests/cbmc/aws-templates-for-cbmc-proofs' a second time, aborting
Failed to recurse into submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/aws-c-common'
Failed to recurse into submodule path 'aws-common-runtime/aws-crt-cpp/aws-common-runtime/s2n'
Failed to recurse into submodule path 'aws-common-runtime/aws-crt-cpp'
I would google the relationship between fatal: '$GIT_DIR' too big
and terraform
Something related to that.
solve it was OS issue $env<i class=”em em-TERRAGRUNT_DOWNLOAD=”C”></i>\Temp” this solved it
2024-08-20
What’s the new GitHub app connected to cloudposse org? Is it safe settings or repository settings app?
The cloudposse newsletters links, at least for the refarch docs, doesnt have a clickable link. I noticed this in other newsletter links too
Here is the link from the newsletter
Cloud Posse just made its reference architecture documentation for AWS publicly accessible. This documentation, previously exclusive to customers, now offers insights into Cloud Posse’s implementation strategies for AWS, Datadog, and GitHub Actions using the Atmos open source framework and Terraform. The documentation covers the usage of tools like geodesic and atmos, infrastructure building with the reference architecture, and deployment maintenance. It also includes an Infrastructure as Code library with references to Terraform components, modules, and GitHub Actions. We now offer … Read More
You can see on that link, there is no link to docs.cloudposse.com. on mobile, you’d have to be ambitious to copy and paste the link and paste it into a browser to access it
2024-08-22
Hey all, I can see that https://github.com/cloudposse-archives/terraform-aws-cloudwatch-agent is in the archive but I can’t see why, does it have a replacement or successor?
Looks like it was never updated with the latest workflows and assumed therefore it wasn’t maintained
We would like to support more CloudWatch, so if it’s something that fulfills your needs and you might contribute to, we can move it out and back into the main org
is the updating with latest workflows thing something that a contributor could do, or would it need CloudPosse team involvement?
I would ask @Igor Rodionov for help with that
Thanks, if I find time to pick it up I’ll ping him
@Erik Osterman (Cloud Posse) should we unarchive the repo then?
@david.gregory_slack once you confirm this fulfills your needs, we can dust it off and move it. @Igor Rodionov hold off for now.