How to efficiently hack / debug initial deployment issues?

[paluh]

Thanks a lot for building nixops and also providing nixops-hetzner out of the box!

I've tried during last few days to debug some issues related to the initial machine provisioning and partitioning. I've ended up commenting some lines and adding some debug prints into the code and rerunning nixops deploy etc. because upload of boostrap file was really slow in case of my network and I needed access to the current rescue mode. I've few related questions:

• Do you think that adding something like boostrapUrl with an image url for download to avoid time consuming upload would be desired?

• Do you think that in debug mode "hetzner rescue mode password" (it is one time password) can be printed out from the nixops-hetzner so when it fails in initial phase it is possible to access this machine in its current state easily?

• I've tried to add some options to HetznerState using attr_property somewhere here and using it here and in machine config (through hetzner.someNewOption) without success. I had received xml parsing errors from nixops package. Could you please suggest me how to add an attribute to the state?

• The most general question is how to debug nixops and nixops-hetzner at the same time?

Sorry if my questions are imprecise or basic but I'm still learning Nix ;-)