Closed ReeceHumphreys closed 5 months ago
Regarding the certificates, seems that you can include them in the NuGet package for the templates:
I tried doing this morning and was running into issues manually installing the templates using dotnet new install path/to/the/template/I/want
as the cert now exists in the NuGet but not permanently in the folder. I think we should just leave it as is for now and can always refine it a bit more in the future!
@bernardnormier brought up the idea of adding more options in the future like an SSL option for TCP!
I tried doing this morning and was running into issues manually installing the templates using dotnet new install path/to/the/template/I/want
Another option would be to look into add a built step to copy them, instead of keeping the copies in git.
The updates look good, with a few considerations:
- Have we considered providing the same feature with the Protobuf templates?
- It wouldn't hurt to include a README file with the templates, clarifying that the provided certificates are for testing purposes.
Definitely! The main goal of this PR was to demonstrate how it could be done and to do it for slice client and server so I can refactor my blog to use these new templates. I'll open issues for these improvements.
Closes #3954
This PR adds a new
--transport
flag to theIceRpc-Slice-Server
andIceRpc-Slice-Client
templates. By default this flag is set toslic
but you can set it toquic
. When set toquic
it will modify the output of the template to produce a QUIC version of the template. For ease of review I have also attached the output from running:The only part that is kinda lame right now is I could not find a way to get the template to copy in the certs from the top level
certs/
directory. As such, we now have a duplicate of theserver.p12
andcacert.der
inside the template folder which is kinda lame. @pepone do you know of any solution for this?