This message was deleted.
# generals
sparse-intern-71089
02/07/2020, 11:07 AMThis message was deleted.
w
white-balloon-205
02/07/2020, 4:41 PM
There’s an
aliaseswhite-balloon-205
02/07/2020, 4:56 PM
Oh - I think I misinterpreted the question actually - that may not be what you are actually asking about here.
white-balloon-205
02/07/2020, 5:25 PM
I actually don’t have a great suggestion on the original question. You would need to cause some input to the PVC that forces replacement to change if-and-only-if the deployment is going to change. That could be hashing the values of key inputs which would cause updates and passing in to a force replace property of the pvc? @gorgeous-egg-16927 might have other thoughts on patterns here.
g
gorgeous-egg-16927
02/07/2020, 7:00 PMThere may be a cleaner way to handle this, but here’s a working example: https://gist.github.com/lblackstone/bc049c94b250fc31e42c4ba375d465a9
t
thousands-london-78260
02/08/2020, 4:40 PMThe problem is that It might not be some input arg that controls the re-creation of the resource. Essentially I would like to not just create a child-parent relationship but create a “pod” where if one of the resources is going to be replaced it will replace (read re-create) all the resources in the pod