[EPIC] ⛰️ Weathertop Foundations

[ford-at-aws]

This epic is to manage the four (4) pre-requisite items that each language owner must accomplish to clear the way for integrating each language with the automation framework.

NOTE: None of these stories will block the remaining automation work outlined in the Quip one-pager.

ANOTHER NOTE: You can use the button below to create stories, but please use the user story found within these Ruby stories:

• Document Ruby dependencies & build steps #3830
• Invoke Ruby tests via CLI #3831
• Tag Ruby tests #3832
• Refine Ruby docker image and mark as GA #4124

---

1. All dependencies are documented for at least 1 service in the Service-level README

This include runtime, language version, and external libraries, and steps if applicable. For interpreted languages, that means dependency resolution. For compiled languages, that means steps for compiling.

• Document Ruby dependencies & build steps #3830
• Document Python dependencies & build steps #4156
• Document Java dependencies & build steps #4157
• Document JavaScript dependencies & build steps #4158
• Document Kotlin dependencies & build steps #4159
• Document Rust dependencies & build steps #4160
• Document PHP dependencies & build steps #4161
• Document C++ dependencies & build steps #4162
• Document .NET dependencies & build steps #4163
• Document Swift dependencies & build steps #4164
• Document Go dependencies & build steps #4165

See example here https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/ruby#get-started

2. Tests can be segregated during invocation/execution based on language best practices

For example, integ vs. unit tags to run each types respectively

• Tag Ruby tests #3832
• Tag Python tests #4175
• Tag Java tests #4176
• Tag JavaScript tests #4177
• Tag Kotlin tests #4178
• Tag Rust tests #4179
• Tag PHP tests #4180
• Tag C++ tests #4181
• Tag .NET tests #4182
• Tag Swift tests #4183
• Tag Go tests #4184

Document in the README, or if you're not already using tagging just add a screen shot.

3. Tests can be executed at the top level directory via single command for each language

This could be a single CLI command or a bash script comprised of multiple commands.

• Invoke Ruby tests via CLI #3831
• Invoke Python tests via CLI #4166
• Invoke Java tests via CLI #4167
• Invoke JavaScript tests via CLI #4168
• Invoke Kotlin tests via CLI #4169
• Invoke Rust tests via CLI #4170
• Invoke PHP tests via CLI #4171
• Invoke C++ tests via CLI #4172
• Create top-level solution to build and Invoke .NET tests via CLI #4043
• Invoke Swift tests via CLI #4173
• Invoke Go tests via CLI #4174

See example here https://github.com/awsdocs/aws-doc-sdk-examples/tree/main/ruby#integration-tests

4. Release Docker images as GA

Part of the Weathertop foundations are images for each language that contain example code, pre-loaded with dependencies and ready to run off the shelf.

While I've done basic work creating a "v1" of each image, it's important for each language owner to "adopt" their language's image and make it reflect the high bar of excellence that we adhere to as a team. Currently, they fall short and are marked as "BETA" as a result.

The goal of this epic is to bring all language Docker images so that they're something we're proud of and can stand by.

There will be one (1) story for each language:

• Refine Ruby docker image and mark as GA #4124
• Refine Python docker image and mark as GA #4125
• Refine Dotnetv3 docker image and mark as GA #4126
• Refine JavaScriptv3 docker image and mark as GA #4127
• Refine Javav2 docker image and mark as GA #4128
• Refine Gov2 docker image and mark as GA #4129
• Refine Kotlin docker image and mark as GA #4130
• Refine PHP docker image and mark as GA #4131
• Refine Swift docker image and mark as GA #4132
• Refine Cpp docker image and mark as GA #4133
• Refine Rust docker image and mark as GA #4134