-
Notifications
You must be signed in to change notification settings - Fork 173
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 C# + SQL Azure template #550
Conversation
Manual test completed, no issues found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates look great, just not sold on the names.
cd482bc
to
a1a5cf2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small questions about what happens if you end up running provision
multiple times. I will admit that I am both excited and scared by the command running technology we are adding, but I can't really think of a better way to do this (all my solutions look like use uniqueString
so we end up with something "unguessable" but it would be easy to compute if you knew all the inputs, which doesn't seem great).
Thinking about what this would look like in TF or Pulumi, as you mention we'd have the random resource there and it would be used to generate a password, but critically, the output would be stored in the state file and not change run to run.
Part of me wonders if we should be using [randomPassword()]
instead of $(randomPassword)
since that's closer to ARM syntax, but that's pretty bike-sheddy.
(need to do some testing, do not merge) |
Tested the new template and command, all looks good. @ellismg please review again! |
Adds password generation capability to AZD CLI
53be81a
to
d805a7f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions - I feel most strongly about us not enumerating the existing KeyVault resources from the deployment if we can, I think that's possible and reasonable to do now that we pass the KeyVault name as a parameter to secretOrRandomPassword
in but if I'm missing something let me know.
Repoman Generation ResultsRepoman pushed changes to remotes for the following projects: Project: todo-csharp-sqlRemote: azure-samples-stagingBranch: pr/550You can initialize this project with: azd init -t Azure-Samples/todo-csharp-sql -b pr/550 View Changes | Compare Changes |
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
Windows
Standalone Binary
Container
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - Thanks for this, Karol. I really enjoyed collaborating with you on the design and I think what we ended up with is pretty great and solve a real pain point in a very good way.
Thank you, Matt, your suggestions and collaboration made it way better than what I could have come up with on my own! |
A bigger change than just the template because we need to add password-generation capability to AZD (for Bicep). Note that if we decide to have an equivalent Terraform template, no extra work will be necessary because Terraform already has password generation built-in.
The changes to deployment provider (renaming
Preview()
toPrepare()
method and havingDeploy()
take aPreparedDeployment
is something @ellismg @HadwaAbdelhalem and @wbreza discussed offline.I will need some help with making this template subject to automated tests and flipping the corresponding repo to public--TIA!
Fixes #450