-
Notifications
You must be signed in to change notification settings - Fork 5
feat: add DeletePackagesAssociatedWithReleases property #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add DeletePackagesAssociatedWithReleases property #15
Conversation
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.", |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
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
delete_packages_associated_with_releases
changes to true.e.g.