rajpalc7
commented
1 year ago List of all affected repositories
https://github.com/BCDevOps/openshift-wiki
https://github.com/BCDevOps/backup-container
https://github.com/bcgov/von-bc-registries-audit
https://github.com/bcgov/met-public
https://github.com/bcgov/nr-arch-templates
https://github.com/bcgov/aries-vcr-issuer-controller
https://github.com/bcgov/jag-lcrb-carla-public
https://github.com/bcgov/eao-inspections-evidence-locker
https://github.com/bcgov/queue-management
https://github.com/bcgov/von-bc-registries-agent
https://github.com/bcgov/digital-journeys
https://github.com/bcgov/biohubbc-platform
https://github.com/bcgov/sso-keycloak
https://github.com/bcgov/sbc-pay
https://github.com/bcgov/met-public
https://github.com/bcgov/platform-developer-docs
https://github.com/bcgov/queue-management
https://github.com/bcgov/devhub-app-web
https://github.com/bcgov/eao-inspections-evidence-locker
https://github.com/bcgov/jag-lcrb-carla-public
https://github.com/bcgov/biohubbc
https://github.com/bcgov/devhub-app-web
https://github.com/bcgov/github-optimization
https://github.com/bcgov/eao-inspections-evidence-locker
https://github.com/bcgov/von-bc-registries-agent-configurations
WadeBarnes
Deprecate and archive the BCDevOps/go-crond repo. The upstream repo has merged the changes that prompted the fork in the first place and has updated the project as well.
Add some documentation to this affect before archiving.
To be completed after https://github.com/BCDevOps/backup-container/issues/98
Review the use of
BCDevOps/go-crondas it is more prevalent than I had thought. Review the following searches and determine how best to proceed.Create a list of all affected repositories. Create tickets for the DITP related repositories that need to be updated. For the rest (other teams repositories) it may be best to make an announcement on Rocket.Chat with the list of the affected repositories.