This message was deleted.
# kubernetess
sparse-intern-71089
08/04/2020, 5:53 PMThis message was deleted.
g
gorgeous-egg-16927
08/04/2020, 6:51 PMI don’t know the answer to that off the top of my head, but I’d guess that they would be deleted.
I think you should be able to fix it by setting aliases on those ConfigFile resources such that the name points to the old file location. This tells the engine that the files are the same, and only the name/location changed.
gorgeous-egg-16927
08/04/2020, 6:52 PMs
shy-tent-25663
08/04/2020, 6:55 PMthe ConfigFiles are generated via the ConfigGroup. Would the alias apply to the ConfigGroup resource itself? Or would I add the alias directly to the stack and re-import?
shy-tent-25663
08/04/2020, 6:55 PMfor each individual configfile
g
gorgeous-egg-16927
08/04/2020, 7:10 PMOh, hmm. The alias would need to be applied to the ConfigFile, but you don’t have direct control of that with a ConfigGroup.
I’m not actually sure what will happen without testing it. Hopefully it will detect that the actual resources haven’t changed, but I need to verify that.
gorgeous-egg-16927
08/04/2020, 7:14 PMOk, I just tested it locally by moving a file to a different directory, and it didn’t change the resources themselves.
gorgeous-egg-16927
08/04/2020, 7:15 PMI think you should be fine to proceed, but you might want to check for yourself on a dev stack or similar
s
shy-tent-25663
08/04/2020, 7:22 PMok thanks!
8 Views