Update web proxy import#2571
Merged
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2571 +/- ##
=========================================
Coverage 83.26% 83.26%
Complexity 1286 1286
=========================================
Files 243 243
Lines 5934 5934
Branches 279 279
=========================================
Hits 4941 4941
Misses 846 846
Partials 147 147 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jonathanpmoraes
referenced
this pull request
in nubank/NuMarquez
Feb 6, 2025
Co-authored-by: phix <peter.hicks@astronomer.io>
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
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.
Problem
Our
./docker/up.shprocess is currently broken due to the fact thathttp-proxy-middlewarewas upgraded.One-line summary:
Updating the import style for the
http-proxy-middlewareChecklist
CHANGELOG.md(Depending on the change, this may not be necessary)..sqldatabase schema migration according to Flyway's naming convention (if relevant)