OSAC-3400: Archive dead osac-aap-ee repository

[eliorerz]

Summary

Sets archived = true on osac-aap-ee's Terraform module (repo_cloudkit_aap_ee in repositories.tf) so the next tofu apply archives it on GitHub.

Why

osac-aap-ee ("OSAC execution environment for AAP") has only 2 commits, both from its creation day (2025-04-08), never touched again. osac-aap's own execution-environment/ directory (added 3 days later, actively maintained since -- most recent commit June 2026) superseded it: its README documents ansible-builder build --tag osac-aap-ee, i.e. osac-aap builds the same-named image in-repo today. Nothing consumes the standalone repo -- no CI publishes it, no image references it. Its Terraform module also has minimal governance (fulfillment-wg push only, no wg-infra admin, no required checks) compared to the real component repos.

This is dead weight left over from before this org's current structure, not a mono-repo migration candidate.

Notes

• This is the first real usage of the archived variable on modules/common_repository -- it's already plumbed through (variables.tf -> main.tf's github_repository.archived), but no repo currently sets it, since the archival work for the actual mono-repo component repos (fulfillment-service/osac-operator/osac-aap/osac-installer) is still pending its own rollback window.
• Deliberately not merging this myself -- archiving a repo is live, hard-to-reverse GitHub state (read-only afterward; un-archiving is possible but disruptive), so this gets a human look first, same as the other repo-state-affecting PRs in this epic.

Test plan

• tofu fmt -check -diff clean
• tofu validate passes (only pre-existing deprecation warnings unrelated to this change, same ones noted in PR OSAC-3364: Register new osac mono-repo in Terraform #148)
• Human review + merge -- the repo actually gets archived on the next tofu apply

[coderabbitai]

Warning

Review limit reached

@eliorerz, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository: osac-project/coderabbit/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d205fd8e-6758-484c-a121-38bc6ba210e0

📥 Commits

Reviewing files that changed from the base of the PR and between 3771c33 and 177bd95.

📒 Files selected for processing (1)

• repositories.tf

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}