Skip to content

Update health check path to /app to avoid 307 redirect#162

Merged
devilleweppenaar merged 1 commit intomasterfrom
chas/1793-scim-bridge-health-check-responding-with-307
Dec 10, 2021
Merged

Update health check path to /app to avoid 307 redirect#162
devilleweppenaar merged 1 commit intomasterfrom
chas/1793-scim-bridge-health-check-responding-with-307

Conversation

@chasdl
Copy link
Collaborator

@chasdl chasdl commented Dec 10, 2021

Because of a 307 Temporary Redirect response code being returned from /, configs using / as the health check are continually failing and recreating the ECS task, resulting in broken bridges.

Prior to release v2.3.0 of the SCIM bridge, hitting GET / would return a 200 if everything was healthy, and therefore was a proper path for health checks. Now with v2.3.0 we are redirecting / to /app in order to serve the new React app, so defining /app as the health check path by default gets us to a working state.

Since release v2.3.0, users can also enable an optional ping server on /ping for health check purposes. This will be the way forward as the default for our helm charts, but this requires the OP_PING_SERVER option to be enabled, so for this ECS Fargate terraform config we'll need to keep it as /app.

@chasdl chasdl mentioned this pull request Dec 10, 2021
Copy link
Contributor

@devilleweppenaar devilleweppenaar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🙌 🎉

@devilleweppenaar devilleweppenaar merged commit 66b1674 into master Dec 10, 2021
@devilleweppenaar devilleweppenaar deleted the chas/1793-scim-bridge-health-check-responding-with-307 branch December 10, 2021 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants