Closed ppastorf closed 2 months ago
If you don't want a lifecycle policy, then turn it off, no?
If both variables are left unset (default values) the module fails to apply because the default is to create an policy, but the default value for the policy is ""
. IMO this creates additional headache to the final user who just wants to quickly use the module.
This PR has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this PR will be closed in 10 days
This PR was automatically closed because of stale in 10 days
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
This is a very simple PR to
change the default of "create_lifecycle_policy" variable to falseavoid breaking during apply phase when bothvar.create_lifecycle_policy
andvar.repository_lifecycle_policy
are left unset.Motivation and Context
If left unset both
var.create_lifecycle_policy
andvar.repository_lifecycle_policy
, Terraform will try to create the policy but using a empty string as argument, leading to the following error:Breaking Changes
There should be none.
How Has This Been Tested?
I have tested locally with Terragrunt. It should work.
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request