Merge pull request #790 from project-kessel/refs

astrozzc · web-flow · commit 8a81d392d4ff · 2026-06-12T15:19:31.000-04:00
[RHCLOUD-31900] Update refs from redhatinsights to project-kessel
diff --git a/.github/workflows/master.yml b/.github/workflows/master.yml
@@ -31,12 +31,12 @@ jobs:
 
       # generate ksil json file
       - name: Run Generate V1-Only Permissions Data for stage
-        uses: RedHatInsights/rbac-config-actions/generate-v1-only-permissions@main
+        uses: project-kessel/rbac-config-actions/generate-v1-only-permissions@main
         with:
           ksl: configs/stage/schemas
           rbac_permissions: configs/stage/permissions
       - name: Run Generate V1-Only Permissions Data for prod
-        uses: RedHatInsights/rbac-config-actions/generate-v1-only-permissions@main
+        uses: project-kessel/rbac-config-actions/generate-v1-only-permissions@main
         with:
           ksl: configs/prod/schemas
           rbac_permissions: configs/prod/permissions
diff --git a/.github/workflows/pr.yml b/.github/workflows/pr.yml
@@ -22,26 +22,26 @@ jobs:
           print-valid-files: true
           strict: false
       - name: Validate Permissions' Dependencies
-        uses: RedHatInsights/rbac-config-actions/validate-permission-dependencies@main
+        uses: project-kessel/rbac-config-actions/validate-permission-dependencies@main
         with:
           permissions_path_pattern: 'configs/*/permissions/*.json'
 
       # Ensure that a proper valid schema is generated
 
       # generate ksil json file
       - name: Run Generate V1-Only Permissions Data for stage
-        uses: RedHatInsights/rbac-config-actions/generate-v1-only-permissions@main
+        uses: project-kessel/rbac-config-actions/generate-v1-only-permissions@main
         with:
           ksl: configs/stage/schemas
           rbac_permissions: configs/stage/permissions
       - name: Run Generate V1-Only Permissions Data for prod
-        uses: RedHatInsights/rbac-config-actions/generate-v1-only-permissions@main
+        uses: project-kessel/rbac-config-actions/generate-v1-only-permissions@main
         with:
           ksl: configs/prod/schemas
           rbac_permissions: configs/prod/permissions
 
       - name: Generate & validate schema
-        uses: RedHatInsights/rbac-config-actions/validate-schema@main
+        uses: project-kessel/rbac-config-actions/validate-schema@main
         with:
           token: ${{ secrets.GITHUB_TOKEN }}
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -12,12 +12,12 @@ This project follows the [Red Hat Code of Conduct](https://www.redhat.com/en/abo
 
 - **Go 1.22+** ([download](https://golang.org/dl/))
 - **Git** for version control
-- **GitHub account** with access to RedHatInsights
+- **GitHub account** with access to project-kessel
 
 ### Local Setup
 
 ```sh
-git clone https://github.com/RedHatInsights/rbac-config.git
+git clone https://github.com/project-kessel/rbac-config.git
 cd rbac-config
 make init                    # Install ksl and generate-v1-only-permissions tools
 make check-go-tools          # Verify installation
@@ -118,6 +118,6 @@ Detailed guidance is available in dedicated files:
 
 - **Technical questions:** Open a GitHub issue
 - **RBAC service questions:** Consult the [RBAC Platform Docs](https://consoledot.pages.redhat.com/docs/dev/services/rbac.html)
-- **Service repository:** [insights-rbac](https://github.com/RedHatInsights/insights-rbac)
+- **Service repository:** [insights-rbac](https://github.com/project-kessel/insights-rbac)
 
 Thank you for contributing!
diff --git a/Makefile b/Makefile
@@ -11,8 +11,8 @@ init:
 	@HASH=$$(git ls-remote https://github.com/project-kessel/ksl-schema-language.git HEAD | cut -f1) && \
 	go install github.com/project-kessel/ksl-schema-language/cmd/ksl@$$HASH
 
-	@HASH=$$(git ls-remote https://github.com/RedHatInsights/rbac-config-actions.git HEAD | cut -f1) && \
-	go install github.com/RedHatInsights/rbac-config-actions/generate-v1-only-permissions/cmd/generate-v1-only-permissions@$$HASH
+	@HASH=$$(git ls-remote https://github.com/project-kessel/rbac-config-actions.git HEAD | cut -f1) && \
+	go install github.com/project-kessel/rbac-config-actions/generate-v1-only-permissions/cmd/generate-v1-only-permissions@$$HASH
 
 check-go-tools:
 	@echo "Checking required Go tools..."
diff --git a/README.md b/README.md
@@ -6,7 +6,7 @@ There is no application code here -- only JSON configs, KSL schemas, and CI auto
 
 | Resource | Link |
 |----------|------|
-| RBAC Service | https://github.com/RedHatInsights/insights-rbac |
+| RBAC Service | https://github.com/project-kessel/insights-rbac |
 | RBAC Platform Docs | https://consoledot.pages.redhat.com/docs/dev/services/rbac.html |
 
 ## Deployment Schedule
diff --git a/docs/integration-guidelines.md b/docs/integration-guidelines.md
@@ -23,7 +23,7 @@ This repository defines RBAC (Role-Based Access Control) permissions and roles f
 2. The **PR workflow** (`.github/workflows/pr.yml`) validates JSON schemas and SpiceDB schemas
 3. After merge to `master`, the **master workflow** (`.github/workflows/master.yml`) automatically:
    - Generates V1-only permissions data from KSL schemas
-   - Converts configs into Kubernetes ConfigMap templates via `RedHatInsights/rbac-config-actions/convert-config`
+   - Converts configs into Kubernetes ConfigMap templates via `project-kessel/rbac-config-actions/convert-config`
    - Validates generated SpiceDB schemas with `authzed/action-spicedb-validate`
    - Creates an automated PR on the `configmaps-schema` branch with the title `[GitHub] - Automated ConfigMap & Schema Generation`
 4. Once the ConfigMap PR is merged, a separate MR must be created in the **app-interface** GitLab repo to bump the `ref` in the `resourceTemplate` for the target namespace, which triggers actual deployment
@@ -124,27 +124,27 @@ Stage may include additional KSL files not yet in prod (e.g., `subscriptions.ksl
 
 Runs on every PR to `master` with these sequential checks:
 1. **JSON Schema validation** via `walbo/validate-json` -- validates all `configs/*/permissions/*.json` against `schemas/permissions.schema` and all `configs/*/roles/*.json` against `schemas/roles.schema` (roles use `strict: false`)
-2. **Permission dependency validation** via `RedHatInsights/rbac-config-actions/validate-permission-dependencies` -- checks `requires` field integrity
-3. **V1-only permissions generation** via `RedHatInsights/rbac-config-actions/generate-v1-only-permissions` -- for both stage and prod
-4. **Schema generation and validation** via `RedHatInsights/rbac-config-actions/validate-schema`
+2. **Permission dependency validation** via `project-kessel/rbac-config-actions/validate-permission-dependencies` -- checks `requires` field integrity
+3. **V1-only permissions generation** via `project-kessel/rbac-config-actions/generate-v1-only-permissions` -- for both stage and prod
+4. **Schema generation and validation** via `project-kessel/rbac-config-actions/validate-schema`
 5. **SpiceDB schema validation** via `authzed/action-spicedb-validate` -- validates the generated `.zed` files for both environments
 
 ### Master Merge Pipeline (`.github/workflows/master.yml`)
 
 Runs on push to `master`:
 1. Generates V1-only permissions for both environments
-2. Converts configs to ConfigMaps and generates schemas via `RedHatInsights/rbac-config-actions/convert-config` (pushes to `configmaps-schema` branch)
+2. Converts configs to ConfigMaps and generates schemas via `project-kessel/rbac-config-actions/convert-config` (pushes to `configmaps-schema` branch)
 3. Validates generated SpiceDB schemas
 4. Creates a PR from `configmaps-schema` to `master` using `gh pr create` if changes exist
 
 ### External Actions Used
 
 | Action | Purpose |
 |--------|---------|
-| `RedHatInsights/rbac-config-actions/validate-permission-dependencies@main` | Validates `requires` field references |
-| `RedHatInsights/rbac-config-actions/generate-v1-only-permissions@main` | Generates V1 compatibility data from KSL |
-| `RedHatInsights/rbac-config-actions/validate-schema@main` | Generates and validates KSL schemas |
-| `RedHatInsights/rbac-config-actions/convert-config@main` | Converts JSON configs to K8s ConfigMaps |
+| `project-kessel/rbac-config-actions/validate-permission-dependencies@main` | Validates `requires` field references |
+| `project-kessel/rbac-config-actions/generate-v1-only-permissions@main` | Generates V1 compatibility data from KSL |
+| `project-kessel/rbac-config-actions/validate-schema@main` | Generates and validates KSL schemas |
+| `project-kessel/rbac-config-actions/convert-config@main` | Converts JSON configs to K8s ConfigMaps |
 | `authzed/action-spicedb-validate@v1` | Validates SpiceDB `.zed` schema files |
 | `walbo/validate-json@v1.1.0` | Validates JSON against JSON Schema |
 
diff --git a/docs/testing-guidelines.md b/docs/testing-guidelines.md
@@ -27,14 +27,14 @@ All files matching `configs/*/roles/*.json` are validated against `schemas/roles
 
 ### 3. Permission Dependency Validation
 
-Uses `RedHatInsights/rbac-config-actions/validate-permission-dependencies` against `configs/*/permissions/*.json`. This validates that any `requires` array entries reference verbs that actually exist for the same app/resource combination. For example, if `create` requires `["read"]`, then `read` must be defined in the same resource array.
+Uses `project-kessel/rbac-config-actions/validate-permission-dependencies` against `configs/*/permissions/*.json`. This validates that any `requires` array entries reference verbs that actually exist for the same app/resource combination. For example, if `create` requires `["read"]`, then `read` must be defined in the same resource array.
 
 ### 4. KSL-to-SpiceDB Schema Generation
 
 The pipeline generates V1-only permissions data and then compiles KSL schemas for both environments:
 
 - **V1 permissions generation**: Reads `configs/{stage,prod}/permissions/*.json` and `configs/{stage,prod}/schemas/*.lst` files to produce `configs/{stage,prod}/schemas/src/rbac_v1_permissions.json` (gitignored build artifact)
-- **Schema compilation**: Uses `RedHatInsights/rbac-config-actions/validate-schema` to compile `.ksl` source files plus the generated JSON into `configs/{stage,prod}/schemas/schema.zed`
+- **Schema compilation**: Uses `project-kessel/rbac-config-actions/validate-schema` to compile `.ksl` source files plus the generated JSON into `configs/{stage,prod}/schemas/schema.zed`
 
 The `.lst` files (`migrated_apps.lst`, `hostsonly_apps.lst`) control which apps get V1-only permission entries in the generated schema.
 
