Conflict against newer ECS 10.x releases due to exception causing hard fail #48
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
Zales0123
approved these changes
Jun 15, 2022
|
Thank you, Michael! 🎉 |
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.
In deprecated-packages/symplify@9d1b0ea (released with 10.2.11), the warning message about the deprecated config syntax was changed from printing a warning to throwing an exception. This effectively means that using ECS >=10.2.11,<11.0 with the
ContainerConfiguratorbased configuration is impossible as the ECS application doesn't handle this exception which causes it to abort. Since this package doesn't yet provide anECSConfigbased configuration, conflicting against newer 10.x releases is the only sane option until the newer syntax is supported.