Skip to content

Farm#31

Closed
stewartshea wants to merge 5 commits into
mainfrom
farm
Closed

Farm#31
stewartshea wants to merge 5 commits into
mainfrom
farm

Conversation

@stewartshea
Copy link
Copy Markdown
Contributor

@stewartshea stewartshea commented May 12, 2026

Note

Medium Risk
Medium risk because it changes the production container base image and adds new automated multi-arch build/push + tagging logic, which could affect runtime compatibility and release publishing. Also updates multiple AWS codebundles to require/provide AWS_ACCOUNT_NAME, which could break runs if that variable isn’t populated by the platform.

Overview
Build/release pipeline: Adds a new build-push GitHub Actions workflow that builds native amd64/arm64 images, runs a smoke test, pushes per-arch digests to GHCR, and then merges them into a multi-arch manifest with a new tag scheme (<ref>-<cc_sha7>-<rt_sha7> plus aliases like latest/pr-<n>). Adds a scheduled/manual release workflow to generate date-based GitHub releases.

Containerization/dev tooling: Updates the production Dockerfile to build from ghcr.io/runwhen-contrib/rw-base-runtime (with an overridable BASE_IMAGE arg) and splits local dev into a new Dockerfile.devcontainer, updating .devcontainer.json to use it.

AWS codebundles: Across several aws-c7n-* bundles, switches SLX/SLI descriptions and Robot task titles to use the human-friendly match_resource.account_name, and threads a new AWS_ACCOUNT_NAME config/user variable through templates and suite initialization (removing ad-hoc account-name lookup in some suites).

Reviewed by Cursor Bugbot for commit 62bb9e5. Bugbot is set up for automated code reviews on this repo. Configure here.

stewartshea and others added 5 commits February 18, 2026 15:10
… for improved clarity in descriptions and aliases.
…t imports of AWS_ACCOUNT_NAME for improved clarity and consistency. Update related templates to include AWS_ACCOUNT_NAME variable.
…with account name for improved clarity. Modify related templates to include AWS_ACCOUNT_NAME variable, enhancing consistency across the codebase.
…tead of account ID references, enhancing clarity and maintainability. Update related templates to ensure uniformity across the codebase.
- Rename existing Dockerfile (codecollection-devtools-based, used for the
  devcontainer / IDE workflow) to Dockerfile.devcontainer and point
  .devcontainer.json at it.
- Add new production Dockerfile based on rw-base-runtime as the CCV
  build target (replaces the external build-system pipeline).
- Add .github/workflows/build-push.yaml: parallel native amd64/arm64
  build matrix (ubuntu-latest + ubuntu-24.04-arm), push-by-digest with
  buildx imagetools manifest merge, catalog-compatible tag schema
  <sanitized_ref>-<cc_sha7>-<rt_sha7>. Builds on push to any branch
  and on PRs; paths-ignore skips docs-only diffs.

Co-authored-by: Cursor <cursoragent@cursor.com>
@stewartshea
Copy link
Copy Markdown
Contributor Author

Closing in favor of #33.

This branch had drifted ~3 months from main and was carrying 4 commits from Feb 18 doing an account_id → account_name refactor that was independently re-done and merged via #28 on the same day. The net file content at farm HEAD matched main HEAD except for the CCV build work that got committed today on top.

GitHub's PR diff renders by replaying every unique commit, so this PR showed 40 files of changes even though only 4 files actually differed at HEAD between farm and main — the rest was touch-and-revert noise from the obsolete duplicate refactor.

#33 contains only the CCV-build commit, rebased onto current main, with a clean 4-file diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant