Deploy to File Share

[SomeRandomVisitor]

This is probably a trivial Posh-ACME.Deploy enhancement to code a deployment target for a file share. This is very useful for multiple real servers behind a load balancer. These real servers can load the certificate from a common file share. The target shall support user-definable naming convention to differentiate for multiple certificates. The idea is that Posh-ACME.Deploy would overwrite the certificate in the file share with the renewed certificate. Posh-ACME.Deploy will need a configurable username and password for the file share. This approach has been implemented by Microsoft via the Central Certificate Store (CCS).

[rmbolger]

I've definitely considered adding this before. I just never got around to it. I can't decide whether it makes more sense to have something generic like Copy-ToFilesystem that has an option like -ForCCS to name files with CCS compatible names....or make a separate CCS specific function like Publish-ToCentralCertificateStore. Both would be useful in different circumstances.

[SomeRandomVisitor]

Funny you mentioned priority. I too have needs for both the CCS (IIS/Exchange) and RHEL (Apache/PHP) hosts behind a load balancer. The CCS is higher priority to me. Thanks for the prompt response!