Skip to content

Conversation

Rose-Northey
Copy link
Contributor

@Rose-Northey Rose-Northey commented Jun 5, 2025

Background

On an octopus server PR a new property was added to enable users to delete packages while still saving releases - DeletePackagesAssociatedWithReleases.

This property was added to the go client. Here we add theDeletePackagesAssociatedWithReleases to the terraform client as well.

[sc-112378]

How to review this PR

  1. Enable the "OCTOPUS__FeatureToggles__DecoupleReleasesFromBuiltInPackageRetentionFeatureToggle" feature toggle.
  2. Set the built in feed settings to be "Always keep packages used by releases and runbook runs on the dashboard".
  3. Ensure the builtIn Feed readonly property, delete_packages_associated_with_releases changes to true.
    e.g.
image

Computed: true,
},
"delete_packages_associated_with_releases": datasourceSchema.BoolAttribute{
Description: "When true, Octopus does not need to keep packages used by releases and runbook runs on the dashboard.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Octopus is keeping releases and runbook runs that are on the dashboard. Maybe check out the docs that Susan is writing for some wording inspiration: OctopusDeploy/docs#2731

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice catch with this! That would have been misleading

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is what I have:

When true, a package which is not associated with a dashboard release or runback run will be deleted after the delete_unreleased_packages_after_days is exceeded.

I'm now wondering if the name: delete_unreleased_packages_after_days is misleading and should be changed to something more generically about package retention.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When true, a package which is not associated with a dashboard release or runback run will be deleted after the delete_unreleased_packages_after_days is exceeded.

Nice, this looks more accurate. Remember that feeds.md also has a description.

I'm now wondering if the name: delete_unreleased_packages_after_days is misleading and should be changed to something more generically about package retention.

It could have a better name. Renaming the existing property would be a breaking change.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We discussed this and agreed to change the description of delete_unreleased_packages_after_days to add clarity to this property without creating a breaking change.

@Rose-Northey Rose-Northey changed the title Add DeletePackagesAssociatedWithReleases property feat: add DeletePackagesAssociatedWithReleases property Jun 9, 2025
@Rose-Northey Rose-Northey requested a review from tothegills June 11, 2025 04:31
Copy link
Contributor

@tothegills tothegills left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

@Rose-Northey Rose-Northey marked this pull request as ready for review June 11, 2025 21:28
@Rose-Northey Rose-Northey merged commit c5967e7 into main Jun 11, 2025
25 checks passed
@Rose-Northey Rose-Northey deleted the rosen/add-DeletePackagesAssociatedWithReleases-property branch June 11, 2025 21:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants