Feature Request: API access to update environment tags

[SlerianDL]

Hi, would it be possible to allow an API call to update snapshots to environment tags we choose.

As we've got a scheduled task to pull the repos every day. But we want to carve them up into monthly tags i.e: feb/mar etc.

Rather than running a scheduled monthly task to pull what the daily is already doing, we want to just update the tag on a schedule per month to the relevant snapshot.

[SlerianDL]

The idea to me is something like this:

/snapshot/<SNAPSHOT_ID>/update-environment/<ENVIRONMENT_NAME>

[lbr38]

Hello
If I understand correctly, you want to point one (or multiple) environment to a snapshot using the API. Is that correct?

[SlerianDL]

Hi thanks for getting back.

I'll explain what I'm trying to achieve:

I've got a bunch of environments:

latest
monthly
jan
feb
mar
apr
may
jun
jul
aug
sep
oct
nov
dec

I've got around 50 repos running daily updates for latest.

Then I have them 50 running every month for the monthly env

The issue I'm having using the crontab, making a task which covers a specific month like say, may. Doing this on around 50~ repos, the cron python script times out due to the sheer load.

So the best idea I had was let the monthly create the snapshots. And then run a command to update that snapshot and point to the relevant monthly environment.

We was thinking of using something like Jenkins to automate that and use the api if that makes things easier.

But having the ability to grab the snapshot id from that date, and point that snapshot id to w/e environment would be perfect.

Which is why I thought this layout might be relevant:
/snapshot/<SNAPSHOT_ID>/update-environment/<ENVIRONMENT_NAME>

[lbr38]

Thanks

I’m still not entirely sure I understand correctly 😅​

In the current design, environments point to snapshots, not the other way around.

If the request is to be able to point an environment to a snapshot using the API, I can confirm that it could be doable with some work. But the reverse is not planned.

I also don’t understand which Python script you’re referring to, or how you’re running tasks with crontab.

[SlerianDL]

Hey thanks for getting back. Sorry I probably didn't explain properly 😂

Our environments are as stated before, each month name, latest and monthly.

The issue is getting the correct snapshot we need to each one.

The cron I was mentioning was the one built into the software:

When I create 52 cron tasks, I get this error when I attempt to go to the frontend:

In the /var/log/nginx/repomanager_error.log we get this error:

2026/05/12 09:14:22 [error] 819#819: *5620 FastCGI sent in stderr: "PHP message: PHP Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/repomanager/controllers/Utils/Cron.php on line 138" while reading response header from upstream, client: 10.42.181.8, server: 127.0.0.1, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/run/php/php8.3-fpm.sock:", host: "repomgr.linux.test.xxxxx", referrer: "https://repomgr.linux.test.xxxxx/"

In total we'd need something like 624 cron tasks 😅

So the work around is using the monthly/daily task. And then at the start of each month, create a update environment task to point it to the month environment I need:

But I can't schedule that so it's a very manual process. This is why I was thinking having an API would make that much easier for us.