Hello! Is there a reason in the action template fo...
# tools
r
Hello! Is there a reason in the action template for the full size test we are using variables for the CEs? we have both (variables & secrets) set up to fetch compute environments, but inconsistently (different names, values need to be updated in two places etc). I would like to remove one set of these from github to avoidn confusion
m
you mean they should all be secrets or all variables?
historically they were all secrets, but that made debugging more difficult, so we switched the non-sensitive ones to variables so the get printed in the log
r
I am happy it being variables, i don't think the CE names are particularly secret. But I will then go ahead and delete the secrets. Too much time has been spend by me and @Maxime Garcia and others trying to figure out why some value isn't what it should be 😄
m
yeah, that was confusing
m
this will break rerunning the action for pipelines with the old pipeline template, but they should just update i guess
p
Variables weren't a thing when we first set this up, that's the only reason we used secrets originally.
Then yeah, backwards compatability..
r
😞 is there a way to reference var as secrets?
or the other way around. Basically can we find a way to just update in one place
for how long do we want to keep backwards comaptibilty for CI runs though?
m
Let's NUKE it
👍🏻 1
p
Yeah fine to nuke it now
r
ok not going to nuke things on Friday at 5:30, but will put it on my list for monday
👍🏻 1
😁 1