chore: Update default ping endpoint - #8657
ppawlowski wants to merge 3 commits into
Conversation
|
My only worry about making this change is for Self Hosted customers who have opened up access based on hostname, They would probably need to be doing deep packet inspection to notice the change as both hostnames should resolve to the same IP addresses (I assume?). |
They point to the same AWS API Gateway but resolve to a different CNAME, thus different IP addresses: |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8657 +/- ##
=======================================
Coverage 77.42% 77.42%
=======================================
Files 469 469
Lines 25346 25346
Branches 6751 6751
=======================================
Hits 19624 19624
Misses 5722 5722
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Description
This pull request updates the default PING endpoint from
ping.flowforge.comtoping.flowfuse.com. Update includes code and documentation changes.Related Issue(s)
Closes https://github.com/FlowFuse/engineering/issues/332
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel