Reputation: 273
Now I did my fair share of googling - and people say it can't be done.
I have some SSM parameters that are only good when deployed first time (and they have to be deployed). Then, a step function changes them. It's a "date" value - it is created with default value initially, but then the lambda updates it. As you can guess, making any changes to my deployments REDEPLOYS parameters that shouldn't be touched anymore - returning them to default (because TF noticed a change). Any way to work around this issue?
Upvotes: 0
Views: 555
Reputation: 273
Of course, lifecycle meta-arguments
lifecycle {
ignore_changes = [
]
}
Specifically, in the case of aws_ssm_parameter
lifecycle {
ignore_changes = [value]
}
Upvotes: 2