{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":848460668,"defaultBranch":"master","name":"haproxy","ownerLogin":"indiebrain","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-08-27T19:56:06.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/59154?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1724789136.0","currentOid":""},"activityList":{"items":[{"before":"aac80c26a6360d3b79768d42078b4f8f439f7064","after":"5809e31a185fce0c3825eacf9c04f76a58396287","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-04T17:40:48.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis introduces the \"init-state {up|down}\" configuration parameter to\nthe server.\n\n- when set to 'fully-up', the server is considered immediately available\n  and can turn to the DOWN sate when ALL health checks fail.\n- when set to 'up' (the default), the server is considered immediately\n  available and will initiate a health check that can turn it to the DOWN\n  state immediately if it fails.\n- when set to 'down', the server initially is considered unavailable and\n  will initiate a health check that can turn it to the UP state immediately\n  if it succeeds.\n- when set to 'fully-down', the server is initially considered unavailable\n  and can turn to the UP state when ALL health checks succeed.\n\nThe server's init-state is considered when the HAProxy instance\nis (re)started, a new server is detected (for example via service\ndiscovery / DNS resolution), a server exits maintenance, etc.\n\nLink: https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"b63964bf0d4a614638813035ae757dfeda03855a","after":"aac80c26a6360d3b79768d42078b4f8f439f7064","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-04T16:56:55.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis introduces the \"init-state {up|down}\" configuration parameter to\nthe server.\n\n- when set to 'fully-up', the server is considered immediately available\n  and can turn to the DOWN sate when ALL health checks fail.\n- when set to 'up' (the default), the server is considered immediately\n  available and will initiate a health check that can turn it to the DOWN\n  state immediately if it fails.\n- when set to 'down', the server initially is considered unavailable and\n  will initiate a health check that can turn it to the UP state immediately\n  if it succeeds.\n- when set to 'fully-down', the server is initially considered unavailable\n  and can turn to the UP state when ALL health checks succeed.\n\nThe server's init-state is considered when the HAProxy instance\nis (re)started, a new server is detected (for example via service\ndiscovery / DNS resolution), a server exits maintenance, etc.\n\nLink: https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"3394ac6ea7dc265721c80622e31327414a564fe3","after":"b63964bf0d4a614638813035ae757dfeda03855a","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-04T16:46:17.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis introduces the \"init-state {up|down}\" configuration parameter to\nthe server.\n\n- when set to 'fully-up', the server is considered immediately available\n  and can turn to the DOWN sate when ALL health checks fail.\n- when set to 'up' (the default), the server is considered immediately\n  available and will initiate a health check that can turn it to the DOWN\n  state immediately if it fails.\n- when set to 'down', the server initially is considered unavailable and\n  will initiate a health check that can turn it to the UP state immediately\n  if it succeeds.\n- when set to 'fully-down', the server is initially considered unavailable\n  and can turn to the UP state when ALL health checks succeed.\n\nThe server's init-state is considered when the HAProxy instance\nis (re)started, a new server is detected (for example via service\ndiscovery / DNS resolution), a server exits maintenance, etc.\n\nLink: https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"d5314bf78ed53d365486b25615fcaf738bdcf17f","after":"3394ac6ea7dc265721c80622e31327414a564fe3","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-03T18:50:58.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis introduces the \"init-state {up|down}\" configuration parameter to\nthe server.\n\n- when not set, the server is considered available as soon as a connection\n  can be established.\n- when set to 'up', the server is considered available as soon as a\n  connection can be established.\n- when set to 'down', the server is initially considered unavailable until\n  it successfully completes its health checks.\n\nThe server's init-state is considered when the HAProxy instance\nis (re)started, a new server is detected (for example via service\ndiscovery / DNS resolution), a server exits maintenance, etc.\n\nLink: https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"f08862324082f783641fcde339e008aa6b3d65d3","after":"d5314bf78ed53d365486b25615fcaf738bdcf17f","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-03T15:29:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nSummary\n---------\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n---------\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis change set introduces the `init-state {up|down}` configuration\nparameter to the server. When `init-state` is set to `down` the\nserver's health checks must succeed before client traffic is\nforwarded when:\n\n1. A new server is detected (for example, via DNS resolution)\n2. A server exits maintenance mode\n3. The HAProxy instance is starting for the first time\n\nWhen init-state is NOT set, or set to UP, the server will be\nconsidered ready to accept traffic; IE backward compatible behavior.\n\nReferences\n------------\n\n- https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"78f825a5f9634095c47bbc1cdf8e4ceed8b76267","after":"f08862324082f783641fcde339e008aa6b3d65d3","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-03T15:27:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nSummary\n---------\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n---------\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis change set introduces the `init-state {up|down}` configuration\nparameter to the server. When `init-state` is set to `down` the\nserver's health checks must succeed before client traffic is\nforwarded when:\n\n1. A new server is detected (for example, via DNS resolution)\n2. A server exits maintenance mode\n3. The HAProxy instance is starting for the first time\n\nWhen init-state is NOT set, or set to UP, the server will be\nconsidered ready to accept traffic; IE backward compatible behavior.\n\nReferences\n------------\n\n- https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":"3668503d709fa182c3c48635702b41fe3bd2b6ee","after":"78f825a5f9634095c47bbc1cdf8e4ceed8b76267","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-09-03T13:16:04.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: add init-state\n\nSummary\n---------\n\nAllow the user to set the \"initial state\" of a server.\n\nContext:\n---------\n\nServers are always set in an UP status by default. In\nsome cases, further checks are required to determine if the server is\nready to receive client traffic.\n\nThis change set introduces the `init-state {up|down}` configuration\nparameter to the server. When `init-state` is set to `down` the\nserver's health checks must succeed before client traffic is\nforwarded when:\n\n1. A new server is detected (for example, via DNS resolution)\n2. A server exits maintenance mode\n3. The HAProxy instance is starting for the first time\n\nWhen init-state is NOT set, or set to UP, the server will be\nconsidered ready to accept traffic; IE backward compatible behavior.\n\nReferences\n------------\n\n- https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: add init-state"}},{"before":null,"after":"3668503d709fa182c3c48635702b41fe3bd2b6ee","ref":"refs/heads/20240827-add-server-init-state","pushedAt":"2024-08-27T20:05:36.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"indiebrain","name":"Aaron Kuehler","path":"/indiebrain","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/59154?s=80&v=4"},"commit":{"message":"MEDIUM: server: optionally req healthchecks when exiting maint\n\nReferences\n------------\n\n- https://github.com/haproxy/haproxy/issues/51","shortMessageHtmlLink":"MEDIUM: server: optionally req healthchecks when exiting maint"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0wNFQxNzo0MDo0OC4wMDAwMDBazwAAAAStAMfP","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOC0yN1QyMDowNTozNi4wMDAwMDBazwAAAASlxreo"}},"title":"Activity · indiebrain/haproxy"}