Hi @mness_8576 ,
For now, archiving is the way to do it. Looking at the code too, it doesn't look like there's even an API to do it...
Here is the code that BuildMaster uses, which clearly just sets the archive flag:
/// <summary>
/// Creates or updates the specified release with the specified data
/// </summary>
public async Task EnsureRelease(string projectName, string releaseNumber, string? releaseUrl, bool? active, CancellationToken cancellationToken = default)
{
using var response = await this.http.PostAsJsonAsync(
"api/sca/releases",
new
{
project = projectName,
version = releaseNumber,
url = releaseUrl,
active
},
cancellationToken
).ConfigureAwait(false);
response.EnsureSuccessStatusCode();
}
Otherwise, we don't have automated deletion or retention policies for archived SCA releases; they don't take up much space (relatively speaking), and we didn't want to commit to retention rules so early on in the feature.
If they become a problem (UI, performance, etc.), it's easy enough to delete a bunch via SQL for the time being... and that'll help us learn how to create policies. And we can add to API and all that :)
Cheers,
Alana
