[FOLIO-3951] Add "Aggies" team to Rancher and platform-complete/platform-core. Created: 22/Dec/23 Updated: 11/Jan/24 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Kevin Day | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | aggies | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | |||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||
| RCA Group: | TBD | ||||||||||||||||||||
| Description |
|
From what I understand, we need a branch on platform-complete and platform-core in Github called "aggies-rancher" that we can build from (similar to how "bama-rancher" is done). The "aggies" team needs to have access to update that "aggies-rancher" branch on platform-complete and platform-core in Github. Once this is done, I am thinking that the aggies team can build the "aggies" namespace from the "aggies-rancher" branch using perhaps the Pipeline Create Namespace From Branch form. We then need this "aggies" team to appear on all of the scratch/Rancher build forms, like the Pipeline Build UI and the Pipeline Manage Scratch Environment Ver 1.2, for example. I believe the other Pipeline Build UI already has "aggies". See also
Alternatively, if there is a reasonable and practical way to have the pipeline point to the TAMU platform-complete https://github.com/TAMULib/platform-complete and the TAMU platform-core (not yet created), then we could manage such things directly without needing access to the platform-complete and platform-core in Github. Perhaps another issue may need to be created for this, but there is also a "tamu" name in Rancher. |