Closed bickelj closed 5 months ago
I am testing this change with a (temporary) tag I pushed onto this commit: 20240328-cb6240c-throwaway
.
Adding \n
to the string didn't work.
I'm testing a regex in the expected body with temporary tag 20240328-340b762-throwaway
.
Woot. It worked. The reason you see a failed job here is that the job checking that the tag is on main correctly failed. We expect tags on main in the vast majority of instances.
@artiz There are two issues revealed above.
expectBody
gets trimmed so we can't do a literal "expect this string followed by a newline".But I don't see an issues section in https://github.com/artiz/poll-endpoint and that this is a fork of (stale?) https://github.com/emilioschepis/wait-for-endpoint. For now I think we're OK but I suppose if GitHub really does remove the functionality we will need to change something.
Without this change, the CI action that asks which version is running in a target environment would fail because of a line terminator difference in the expected string versus the returned string.
This change attempts to fix the issue by adding an escaped endline to the expected response body.
Issue #106 Auto-deploy to production