You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the HA proxy config needs to be written in a JSON format that goes through a translation layer. This translation layer expects certain JSON fields, and thus, restricts the ability to fully customize the HA proxy configuration.
For example, I am unable to create the catch all for the jellyfish API using the line default_backend api_backend because the JSON layer won't let me use it anywhere. There are some hacky ways to get around it, but not everything works and a hacky solution is a bad solution.
Currently, the HA proxy config needs to be written in a JSON format that goes through a translation layer. This translation layer expects certain JSON fields, and thus, restricts the ability to fully customize the HA proxy configuration.
For example, I am unable to create the catch all for the jellyfish API using the line
default_backend api_backend
because the JSON layer won't let me use it anywhere. There are some hacky ways to get around it, but not everything works and a hacky solution is a bad solution.See this flowdock thread for more: https://www.flowdock.com/app/rulemotion/p-cyclops/threads/EnUxWKD10BannateqlRS_M2Sf29
The text was updated successfully, but these errors were encountered: