Closed henrykie closed 2 months ago
@GrzesiekO want to take a stab at this?
Sure
/var/log/p4_configure includes the HAS extension configuration logging, and that is where I was able to detect the failure. Maybe we need to pass arguments to p4_configure shell script with flags to handle null values?
/var/log/p4_configure includes the HAS extension configuration logging, and that is where I was able to detect the failure. Maybe we need to pass arguments to p4_configure shell script with flags to handle null values?
I have a fix with extended configuration for the p4_configure so instead of providing raw values in parameters it will use these flags: --nfs hxmetadata=<>, hxlogs=<>, hxdepots=<> --ebs hxmetadata=<>, hxlogs=<>, hxdepots=<> --auth user=<>, passwd=<> --has hasurl=<>
we still need p4d type (master or replica). I am also getting some strange startup behavior - should p4_setup report successful binary installation? The last message it reports is missing p4 binary, and then it attempts to download missing binaries.
Fixed in PR #239 all features added:
Arm64 support
Long parameters for p4_configure:
"Options:"
--p4d_type
Fixed as per above and PR #239
Expected Behaviour
When no
helix_authentication_service_url
is specified in the Helix Core module the HAS extension should not be configured.Current Behaviour
When no
helix_authentication_service_url
is specified the HAS extension attempts to configure against a null URL and fails thus preventing Helix Core startup.Possible Solution
Adjust the
p4_configure.sh
script and theuser_data
in the Helix Core module to support null HAS URL variables.Steps to Reproduce
Provision a helix core server module without specifying
helix_authentication_service_url
Cloud Game Development Toolkit version
latest