-
Notifications
You must be signed in to change notification settings - Fork 21.8k
Update flask postgres tutorial with clarifications and more information #14885
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
Conversation
…ain sku-name further. Fix command output
…ing resource cleanup
@nnja : Thanks for your contribution! The author, @berndverst, has been notified to review your proposed change. |
CC @cephalin |
Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. When you work in the private repo, after you review staging and fix all validation issues, you can add the sign-off comment to let the reviewers know the updates are ready to be merged. Read about article authors working in the public repo for more information. Would you close this pull request and submit the content in a pull request in the private repo, so automation can take the corresponding action? Thank you. |
@nnja Actually also we're in the process of updating the tutorial to target the Python built-in image. Let's merge this change into that work because there will be quite a bit of structural changes to the sample repo. |
@nnja please close this now in lieu of the other PR |
Made the following changes to update the tutorial and clarify some of the steps:
sku-name
value on the Postgres instance creation with one of a lower price tier, and added an explanation of what thesku-name
flag is used for.Includes clean up for the sample code, via Azure-Samples/docker-flask-postgres#3