Perforce networking refactor

[henrykie]

Issue number:
Closes #402
Closes #408

Summary

Networking updates to Perforce modules. Helix Core now supports plaintext configuration. This allows TLS termination to be handled by an NLB in front of the Helix Core server. ALB creation for Helix Swarm and Helix Authentication Service is now optional, allowing shared ALBs created in higher order or root modules to forward requests to target groups output by these modules.

Changes

Please provide a summary of what's being changed

• Adding plaintext option to Perforce Helix Core module. This disables the ssl: prefix on the Helix Core server directly, and does not generate self-signed certs. We recommend using an NLB in front of the Helix Core server for TLS termination when using this option.
• Adjusted ALB creation for Helix Swarm and Helix Authentication Service. New versions allow creation of a single ALB (optional) that can be labeled as internal or internet facing. Regardless of whether an ALB is created the service target group is provided as an output. This allows users to configure more complex networking setups in their root module.
• Minor changes to variable names, and optional output creation

User experience

Please share what the user experience looks like before and after this change

• Users switching to the new version may need to update their networking configurations for Helix Swarm, Helix Authentication Service and Helix Core.
• The Perforce Complete example now runs Helix Core, Helix Swarm, and Helix Authentication Service behind a single NLB. 1666 traffic is forwarded to Helix Core (with TLS termination at the load balancer), and 443 traffic is forwarded to a shared ALB for both Helix Authentication Service and Helix Swarm. This ALB uses hostname header rules to forward traffic to the appropriate target group.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have performed a self-review of this change
• Changes have been tested
• Changes are documented

Is this a breaking change?

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created might not be successful.

[GrzesiekO]

Approving - all good.

[GrzesiekO]

Resolved conversations - approving.