Skip to content
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

Fixed an ElasticBeanstalk deployment issue for Linux platform where Procfile was sometimes being generated with incorrect entrypoint when multiple runtimeconfig.json files were present. #345

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

ashishdhingra
Copy link
Contributor

@ashishdhingra ashishdhingra commented Nov 8, 2024

Issue #, if available: #285

Description of changes:
Fixed an ElasticBeanstalk deployment issue for Linux platform where Procfile was sometimes being generated with incorrect entrypoint when multiple runtimeconfig.json files were present.

NOTE:
Refer Using a Procfile to configure your .NET Core on Linux Elastic Beanstalk environment where it shows below example to configure 2 web applications.

web: dotnet ./dotnet-core-app1/dotnetcoreapp1.dll
web2: dotnet ./dotnet-core-app2/dotnetcoreapp2.dll

The PR supports one web application as of now to conform to existing logic.
CC @normj


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@ashishdhingra ashishdhingra force-pushed the user/ashdhin/DotnetEB-Procfile-Linux-Issue285 branch from 387264b to 998676a Compare November 11, 2024 19:01
…rocfile was sometimes being generated with incorrect entrypoint when multiple runtimeconfig.json files were present.
@ashishdhingra ashishdhingra force-pushed the user/ashdhin/DotnetEB-Procfile-Linux-Issue285 branch from 998676a to 3bc9f75 Compare November 12, 2024 17:52
@ashishdhingra
Copy link
Contributor Author

ashishdhingra commented Nov 20, 2024

Based on discussion with @normj this is also an issue with AWS .NET Deploy tool. So once we determine optimal fix, we should also port this to deploy tool as part of separate backlog item and PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants