feat: Add space default lifecycle retention polcies #120
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
|
|
||
| ### Optional | ||
|
|
||
| - `quantity_to_keep` (Number) The quantity of items to keep. |
| Read-Only: | ||
|
|
||
| - `id` (String) The ID of the retention policy. | ||
| - `retention_type` (String) The type of retention policy. |
There was a problem hiding this comment.
It would be great to have a little description of what each retention type means since the user will only have this for context and may no know what the short names mean. maybe we can borrow some of the descriptions from here:
octopusdeploy_framework/datasource_space_default_retention_policies.go
Outdated
Show resolved
Hide resolved
octopusdeploy_framework/schemas/space_default_lifecycle_release_retention_policy.go
Outdated
Show resolved
Hide resolved
|
|
||
| ### Required | ||
|
|
||
| - `strategy` (String) The strategy for the retention policy. |
There was a problem hiding this comment.
might be good to have a description here too for people who are unfamiliar. Check out lifecycle.go for examples that could be quite similar (minus mention of default).
|
|
||
| # octopusdeploy_space_default_lifecycle_release_retention_policy (Resource) | ||
|
|
||
| Manages a space's default lifecycle release retention policy. |
There was a problem hiding this comment.
Could be good to have something like:
If a lifecycle resource has "strategy = default", the space_default_lifecycle_release_retention_policy will define the retention for that lifecycle resource.
Could be good to have something on this page which mentions that the initial default strategy for all spaces is "Forever".
docs/resources/space_default_lifecycle_release_retention_policy.md
Outdated
Show resolved
Hide resolved
octopus-hideaki
force-pushed
the
fnm/space-default-retention-lifecycle
branch
from
4cb7723 to
03e5e57
Compare
2 participants
New resources:
New datasource:
These resources are a little different from other resources and data sources in that they are singletons. So it should not be created nor deleted. Instead, these are brought into or out of the control of Terraform instead.
[sc-126254]