Skip to content

revert: undo scale-set orchestration example - #5403

Merged
edersonbrilhante merged 2 commits into
feat-scale-set-terraform-wiringfrom
revert-scale-set-example
Sep 10, 2026
Merged

edersonbrilhante merged 2 commits into
feat-scale-set-terraform-wiringfrom
revert-scale-set-example

Conversation

@edersonbrilhante

Copy link
Copy Markdown
Contributor

Description

Revert the changes introduced by merged PR #5378. This removes the scale-set example, its MiniStack fixtures, and the related workflow/module wiring changes while preserving the later #5350 type-normalization fix.

Test Plan

  • Ran git diff --cached --check before commit.
  • Commit hooks passed Terraform formatting and merge-conflict checks.

Related Issues

Reverts #5378.

@edersonbrilhante
edersonbrilhante requested review from a team as code owners September 10, 2026 18:45
@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@edersonbrilhante
edersonbrilhante merged commit e31d71d into feat-scale-set-terraform-wiring Sep 10, 2026
47 checks passed
@edersonbrilhante
edersonbrilhante deleted the revert-scale-set-example branch September 10, 2026 18:56
edersonbrilhante added a commit that referenced this pull request Sep 17, 2026
## Description

Restore the multi-runner scale-set orchestration example removed by
revert PR #5403, replacing merged PR #5378.

The example provides the Terraform configuration, provider locks,
outputs, and documentation needed to deploy an ECS scale-set controller
with the EC2 runner compute provider. It is intentionally limited to the
example and its generated/provider metadata; the reusable MiniStack
fixture support and ECS/MockServer lifecycle smoke test are provided by
the follow-up PRs.

## Test Plan

- Terraform formatting passed through the repository hooks.
- Merge-conflict checks passed.
- Parent-branch Terraform checks passed after the idle-configuration
correction.
- No live AWS deployment was performed for this example-only PR; CI
validation remains the authoritative deployment check.

## Related Issues

Depends on #5350. Replaces #5378.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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