feat: propagation watch and debug header #1061
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces two things:
1 - An automatic header in the response phase, including a deployment ID; this helps debug projects that use caching in some way.
2 - A pooling observing the propagation of the first deploy (status != 404). It displays a message showing the edges while the project has not yet propagated.
watch.mp4
One detail: we do not use the prefix as
deploy-version, because it refers to the storage. In the future, a user may want to make a change in computable code, but use a different version of the same storage. Perhaps, in the future it will be necessary to change the prefix tostorage-versionor something like that.