-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[Sample] Update C# hello world serving sample according to Microsoft docs, to multistep build #1732
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
[Sample] Update C# hello world serving sample according to Microsoft docs, to multistep build #1732
Conversation
|
Hi @Welkie. Thanks for your PR. I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
Hi Welkie, thanks for the PR! I'm not familiar enough with C# to evaluate the practice here but in looking at the linked article, it makes sense. Two minor points of feedback:
I see this change also switches the Container Registry away from Docker Hub. I'm not sure if there is a policy on this in the knative project, however, the comment referring to the container URL in Docker Hub seems like it should be updated if this is kept. /assign grayside |
…est of samples. Change link in Dockerfile to point to Microsoft site, not Docker Hub.
|
Changes made. The comments should reflect the rest of the samples now. Note that the reason I originally linked to the Docker Hub page at the top of the Dockerfile is because that still appears to be how Microsoft intends people to "discover" the image. https://hub.docker.com/_/microsoft-dotnet-core-aspnet/ You can see how they give a sample |
…harp-hello-world-serving-sample
|
Hi Welkie, thanks for making the changes. If Microsoft prefers to direct people to Docker Hub, I'm okay with keeping that link. Can we add a similar link for the second stage? Also, the README needs to be updated to match the Dockerfile. Sorry for asking for so many minor changes! I've tested the new Dockerfile locally and this works. |
…ch stage of build. Updated README.md file to reflect new Dockerfile.
|
@grayside No problem. This should be good now. It's got the link at the top of each stage of the build in the Dockerfile, and they're Docker Hub links. The readme is up to date now too. |
…:welkie/docs-1 into update-csharp-hello-world-serving-sample
|
@grayside Ready for a review. Made the changes you requested and included a fix for an issue @PicardParis caught. |
|
/lgtm |
|
Do you need me to integrate the latest changes on the base branch before this can be merged? |
|
/approved Sorry for the wait, @mattwelke ! Thanks for your contribution. |
|
I meant -- /approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattwelke, samodell The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Proposed Changes
Tested by building the image before and after this Dockerfile change and ensuring they both worked the same way (responded to requests on a port specified by PORT env var).