Skip to content

Update README.md innabox references to osac project #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DakCrowder merged 1 commit into from
Apr 1, 2026
Merged

Update README.md innabox references to osac project #65

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
# Innabox Github configuration
# Open Sovereign AI Cloud Github configuration

This repository contains [OpenTofu] plan to manage the [innabox] GitHub organization.
This repository contains [OpenTofu] plan to manage the [osac-project] GitHub organization.
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 1, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Search for all remaining references to "innabox" in the codebase

echo "=== Searching for 'innabox' references in all files ==="
rg -i 'innabox' -n -C2

echo -e "\n=== Files containing 'innabox' ==="
rg -i 'innabox' --files-with-matches

Repository: osac-project/github-config

Length of output: 689

Update innabox references in infrastructure code to match osac-project documentation.

The README declares this repository manages the osac-project GitHub organization, but two infrastructure files still reference innabox:

  • backend.tf:8 — State file key: "innabox.tfstate" should reflect osac-project
  • repositories.tf:83 — Repository description: "Argocd apps to deploy resources on the innabox cluster" should reflect the current organization context

Update both files to maintain consistency between documentation and infrastructure code.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 3, The README says this repo manages the osac-project org,
but infra still uses "innabox" — update the state key string "innabox.tfstate"
in backend.tf to something reflecting the org (e.g., "osac-project.tfstate") and
change the repository description string in repositories.tf currently set to
"Argocd apps to deploy resources on the innabox cluster" to reference the
osac-project context (e.g., "Argocd apps to deploy resources on the osac-project
cluster" or similar wording matching org docs); locate the exact literals
"innabox.tfstate" and the description string in backend.tf and repositories.tf
and replace them accordingly.

Copy link
Copy Markdown
Contributor Author

@DakCrowder DakCrowder Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is solely focused on the readme - I'm also unsure if changing the backend file won't result in some changes to the terraformed state when i don't want to deal with right now.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 1, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@DakCrowder, that's a totally valid call — keeping this PR focused on the README makes sense.

Your caution about backend.tf is well-founded. Renaming the state key (e.g., from "innabox.tfstate" to "osac-project.tfstate") without first migrating the existing state would cause OpenTofu to treat the infrastructure as brand new, potentially resulting in destructive plan changes. A proper migration would require something like tofu state mv or reconfiguring the backend carefully.

Would you like me to open a follow-up issue to track the remaining innabox references in backend.tf and repositories.tf, so they can be addressed separately with the appropriate care?



[innabox]: https://github.com/innabox
[osac-project]: https://github.com/osac-project
[opentofu]: https://opentofu.org/

## How does it work?
Expand Down Expand Up @@ -78,7 +78,7 @@ In general, you won't need to do this: the configuration is applied when a pull

1. Acquire GitHub credentials.

In order to apply the configuration, OpenTofu needs administrative access to our organization. You will need a token with at least `admin:org` and `repo` privileges for the `innabox` organization. This should be provided in the `GITHUB_TOKEN` environment variable.
In order to apply the configuration, OpenTofu needs administrative access to our organization. You will need a token with at least `admin:org` and `repo` privileges for the `osac-project` organization. This should be provided in the `GITHUB_TOKEN` environment variable.

[nerc]: https://nerc.mghpcc.org/

Expand Down
Loading