kittyfisto / dploy Goto Github PK

A distributor should only be able to connect to a node and execute commands if the distribute has a signed certificate with which it can authenticate itself to the node. Furthermore, a node should be able to list the certificates which it accepts and it must be possible to revoke a certificate on a node.

Currently connections between distributor and node are not secured in any way: They shall be secured using SslStream.

It should be possible to list the available entry points in a script.

Example: Distributor.exe list Foo.cs

A step such as CopyFile displays a meaningful error message such as "Cannot access the file 'bla bla'", but it doesn't specify the machine where the error occurred. The latter would be very help and shall be included.
Example:

Machine: Simon-PC

All operations triggered via a remote computer shall be logged on a node using ETW. In the end, it shall be possible to inspect who copied / executed what on a node using eventvwr.exe

If a connection to an incompatible node is established, then an appropriate error shall be displayed. Detecting the incompatibility shall be automatic so no developer action is needed.

Example: A node shall always provide a method which returns a description of the methods implemented by that node. If the node is missing a method which the client expects, then the node is incompatible.

Similar to MSBuild targets, it should be possible to specify the entry point.
If none has been specified, then Main() should be called. This way a single script file can be used
for multiple purposes.

Example:

Distributor.exe --script bla.cs --entrypoint Deploy
Distributor.exe --script bla.cs --entrypoint Delete
Distributor.exe --script bla.cs --entrypoint Install