Allow granular usage controls and logs to see what has changed
N
Nick Oakes
It would be helpful to set storage usage/retention on a per project or even per workflow level. Additionally, having the ability to see what user and when these usage settings are changed.
This would be beneficial for large organizations as there can be many admins between different teams with no easy way to differentiate who or what team is changing settings. If storage retention periods need to be kept high for a single project, any other project could now attribute to increased storage costs as the retention period must be kept high, or introduce logic to clear caches to only certain projects.
Autopilot
Merged in a post:
Enhanced Granular Controls for Organization Admins
L
Libby Ly
Org admins need more granular control options to better manage user access and permissions within their organizations. These enhanced controls would help admins proactively manage their billing by providing greater visibility and control over who can consume credits and trigger commits. This increased granularity would reduce unexpected billing scenarios and give teams the administrative tools needed to optimize their CircleCI usage and costs.
S
Steve Ruble
Perhaps a simple way would be to allow the
save_cache
command to specify how long the cache should be retained for, subject to an upper limit based on the project or global retention settings.Chris Cerk
Posting to add support for this idea.
Storage usage/retention on a per project basis would be extremely useful.
Ideally
- Assigning projects to retention "groups" which could be named or have labels.
- Having a fallback default of the global usage/retention settings that exists today.