Testing 5.x
#718
Replies: 1 comment
-
With the deprecation of I noticed the introduction of just a portion of this block for brevity:
Yields errors like Please advise. Thank you |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As promised in #709 (comment) to @hyder (also paging @devoncrouse ) I've started testing 5.x against one of my configurations.
My aim for now is to reach a clean (or equivalent) plan to what I have deployed right now and then go from there.
The text below is a bit of a consciousness stream, I appreciate a lot the work you guys are doing here, no offense intended.
My starting configuration is below. What I've noticed, in no particular order:
You need to merge 12345ieee/terraform-oci-oke@d8428be for the usual provider reasons, or I (and anyone else) can't even init terraform.
A lot of the module variable are severely underspecified,
variable "worker_pools" { type = any }
is by far the worst offender.Terraform 1.3 (which I suggest you adopt, up from 1.2) brings optional map parameters, I've started fully typing the map variables in my custom modules and I'm a big fan of it, but I understand my annoyance could also be mitigated by precise documentation.
Nearly every resource name changed, a ton of
moved
blocks should be added (Terraform version is already > 1.1 so you have them) and kept till, say, 5.1 to let people transition cleanly.I list them below from the PoV of the root module, but they should go in the appropriate (sub)module(s) of the oke module.
Of course my set is non-exhaustive, but it makes my configuration plan with the destruction of seclists/nsg/nulls only, no real cloud recreation.
Nested tag maps, I get the same issue of Explicitely type tag map variables in oke submodule #709 and cluster tag doesn't allow more than 8 freeform tags. #698 , but there are also mistakes in parameter passing, which went uncaught due to the lack of explicit typing as discussed in 2.
I fix them all in 12345ieee/terraform-oci-oke@224b121 , you need to merge it or nonempty tags literally break, but once again the maps should be fully typed.
It's not really possible to write
moved
blocks for seclists and nsgs, as the whole structure changed, but it's not really a problem, as they don't represent real hardware, I cannot be sure my configurations match, this is a case of testing and tweaking the parameters.I'm missing a couple features, I list the associated variables:
I leave my new config at the bottom, this mostly plans cleanly now, but if I were to do this for real it'd need to do this on a test cluster, check the routing works, etc...
I have not reviewed the code itself except from the variables interface and what I needed to reverse engineer functionality, I can check parts if needed.
Nice work guys, looking forward to trying some new features, you can reply to this discussion if you'd like me to review or try some more stuff.
Old config:
Moved blocks:
New config:
Beta Was this translation helpful? Give feedback.
All reactions