login
@tom_tyler This can be done using technique from: https://github.com/perforce/p4prometheus/blob/master/scripts/install_p4prom.sh#L103 And: https://github.com/perforce/p4prometheus/blob/master/scripts/install_p4prom.sh#L173
Andy is testing on AMI Builder and we can merge it back??
@robert_cowham I was working on adding my changes in but then noticed this:
https://swarm.workshop.perforce.com/projects/perforce_software-helix-installer/jobs/HI-54
Based on that job I think we can close this.
Yup, I could close HI-91 as a duplicate of HI-54, but better still I'll just associate it with CL @28662 already fixed in the dev branch. I just need to fire up the regression test suite and fix it.
Hi, Folks! Sorry for the confusion -- the change for this was shipped already! It is available now as of HelixInstaller 2022.1/28663 (2022/03/08).
@tom_tyler
This can be done using technique from:
https://github.com/perforce/p4prometheus/blob/master/scripts/install_p4prom.sh#L103
And:
https://github.com/perforce/p4prometheus/blob/master/scripts/install_p4prom.sh#L173
Andy is testing on AMI Builder and we can merge it back??
@robert_cowham I was working on adding my changes in but then noticed this:
https://swarm.workshop.perforce.com/projects/perforce_software-helix-installer/jobs/HI-54
Based on that job I think we can close this.
Yup, I could close HI-91 as a duplicate of HI-54, but better still I'll just associate it with CL @28662 already fixed in the dev branch. I just need to fire up the regression test suite and fix it.
Hi, Folks! Sorry for the confusion -- the change for this was shipped already! It is available now as of HelixInstaller 2022.1/28663 (2022/03/08).