Open asteel-gsa opened 3 months ago
Terraform plan for dev
:memo: Plan generated in Pull Request Checks #3643
Terraform plan for meta
:memo: Plan generated in Pull Request Checks #3643
So... basically what is being done here, and im not entirely sure this is the correct way of doing this, but due to me being unable to bootstrap things locally, I had to rely on grabbing specific things from cgov..
~>0.53.1
in providers-managed.tf
filesterraform init -upgrade
in preview, staging, production, dev, meta
v1.0.0
from v0.9.1
recursive_delete
as its no longer used in the modules~>0.53.1
and is attempting to overwrite the resources with it, which is okay, because they are checked in the same version for the providers. I am a little hesistant on this and would like to get mogul's opinion on how we should do this, if there is a better way. We are unable to upgrade from v0.9.1
to v.1.0.0
otherwise, due to our locks being ~>0.51.3
, where this was accessible in v0.9.1
release, however, no longer available in v1.0.0
release.
current status: ✅
Overall Coverage
Lines Covered Coverage Threshold Status 18378 16736 91% 0% 🟢 New Files
No new covered files...
Modified Files
No covered modified files...
updated for commit:
76d567a
by action🐍
This appears to be operational, however, we should proceed with caution and discuss if we want to fully update everything at some point
@mogul if you by chance have a moment, I would greatly appreciate your 👀 on this, as I would like to ensure the terraform upgrade was done in a safe and secure way, to avoid any possible system breakage.
delete_recursive_allowed = false
to to ensure the defaulttrue
value does not get appliedv1.0.0
, bringing us up to date with https://github.com/GSA-TTS/terraform-cloudgov~>0.53.1
for compatability withv1.0.0
aboverecursive_delete = true
from modules as it has been depreciated