-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix rabbit mq bindings in manifest. #1985
Conversation
/cc @DamianEdwards I think we might need to revise our guidance in samples about referencing the db creation project directly, it is best for the db context to be in its own library. |
/backport to release/8.0-preview3 |
Started backporting to release/8.0-preview3: https://github.com/dotnet/aspire/actions/runs/7720241404 |
@mitchdenny backporting to release/8.0-preview3 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Fix rabbit mq bindings in manifest.
.git/rebase-apply/patch:142: trailing whitespace.
.git/rebase-apply/patch:165: trailing whitespace.
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M Aspire.sln
Falling back to patching base and 3-way merge...
Removing playground/eShopLite/infra/main.parameters.json
Removing playground/eShopLite/infra/main.bicep
Removing playground/eShopLite/infra/eshoplite/app.bicep
Removing playground/eShopLite/azure.yaml
Auto-merging Aspire.sln
CONFLICT (content): Merge conflict in Aspire.sln
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Fix rabbit mq bindings in manifest.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@mitchdenny an error occurred while backporting to release/8.0-preview3, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
* Fix rabbit mq bindings in manifest. * Use 3 tag for RMQ, and checkin manifest.
* Fix rabbit mq bindings in manifest. * Use 3 tag for RMQ, and checkin manifest.
* Fix rabbit mq bindings in manifest. * Use 3 tag for RMQ, and checkin manifest.
Fixes #1973
... and then some. I change
AppHost
over to using Rabbit MQ container since we don't yet haverabbitmq.v0
support in AZD. This allows us to deploy eshoplite via AZD. As part of that work I had to move the EF data context that was in CatalogDb app into a shared library so it could be shared by CatalogService. Having CatalogService referencing CatalogDb created some publish time issues and this was the easiest workaround.Whilst the app now deploys cleanly to AZD there are some issues associated with scaling. Specifically the rabbit mq container scales to zero. I am not 100% sure but I don't think you can scale up when you aren't using a HTTP binding in ACA.
Microsoft Reviewers: Open in CodeFlow