feat!: migrate to Go #818
Draft
feat!: migrate to Go #818
Conversation
This file contains hidden or 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
BREAKING CHANGE: This migrates the entire service over to Go by default, rather than the Node.js implementation. This means the entire service has been rewritten (but with the same acceptance tests). This comes with a whole lot more configurability, and enables us to implement much stronger security measures in the service.
|
🐳 Docker image built and pushed to GitHub Container Registry. You can pull it using: docker pull ghcr.io/grafana/grafana-image-renderer:dev-pull-818-5977a51d8337f3177dcdab483da7dae5771fefdfWarning This is a development image and should not be used in production. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 mints v5.0.0. We'll be merging this around when we deploy the Go service to prod3 & prod4. Until then, it's intended to stay a draft.
BREAKING CHANGE: This migrates the entire service over to Go by default, rather than the Node.js implementation. This means the entire service has been rewritten (but with the same acceptance tests).
This comes with a whole lot more configurability, and enables us to implement much stronger security measures in the service.