To be elaborated on, but probably at harbor install/setup time
Note that there's a combo of policies for the toolforge project:
Then we have to manually keep the last 10 immutable images (like we do with maintain-harbor on tools-harbor currently).
One issue of doing it at deploy/install time is that you can't change them after without redepolying.
Note also that maintain-harbor already manages the policies for all the other projects in harbor.
Then maybe add this to maintain-harbor too and make it a source of truth for any config that need to happen after deploy time?
raymond-ndibe opened https://gitlab.wikimedia.org/repos/cloud/toolforge/maintain-harbor/-/merge_requests/47
Draft: [maintain-harbor.jobs] manage policies and robot accounts
raymond-ndibe opened https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/881
Draft: [maintain-harbor] add tests and configurations for new maintain-harbor jobs
What is this stalled on?
Nothing, I just wanted to show that nobody is working on it, but "Open" is probably a better status.
raymond-ndibe closed https://gitlab.wikimedia.org/repos/cloud/toolforge/maintain-harbor/-/merge_requests/47
[maintain-harbor.jobs] manage policies and robot accounts
raymond-ndibe closed https://gitlab.wikimedia.org/repos/cloud/toolforge/toolforge-deploy/-/merge_requests/881
[maintain-harbor] add tests and configurations for new maintain-harbor jobs