feat: download correct binary when in FedRAMP environment

[adamconnelly]

Description of the change

I've updated the startup script to check whether it's connecting to the MQTT broker for our FedRAMP environment. If so it downloads the FedRAMP-specific version of the launcher.

Type of change

• Bug fix (non-breaking change that fixes an issue);
• New feature (non-breaking change that adds functionality);
• Breaking change (fix or feature that would cause existing functionality to not work as expected);
• Documentation (a documentation or example fix not affecting the infrastructure managed by this module);

Checklists

Development

• All necessary variables have been defined, with defaults if applicable;
• The code is formatted properly;

Code review

• The module version is bumped accordingly;
• Spacelift tests are passing;
• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached;
• This pull request is no longer marked as "draft";
• Reviewers have been assigned;
• Changes have been reviewed by at least one other engineer;

[jmfontaine]

👍

[adamconnelly]

@jmfontaine @Apollorion @frncmx I've updated this to be a bit simpler based on Joey's suggestion. Instead of a new var, I'm just looking at the MQTT broker hostname to decide which binary to download. This means it'll just work seamlessly for customers with no extra configuration for FedRAMP.

Apologies that I squashed all the changes instead of pushing separate commits - I just did it by accident without thinking.

[frncmx]

Apologies that I squashed all the changes instead of pushing separate commits - I just did it by accident without thinking.

I still read less, than before. 😆

lgtm; like

[TheOutdoorProgrammer]