terraform/rpc
Sander van Harmelen a79c987538 Reverting a few lines from PR #2406
As discussed with @mitchellh and @phinze we don’t need to randomize in
order to get infinite ID’s. When we hit the highest possible number and
add `1` it will just wrap back to `0`, which is just fine with regards
to how Terraform works and uses these ID’s.

Tested this by setting the initial value of `m.nextId` to `4294967293`
where the maximum is `4294967295 `. So with some additional logging it
clearly showed it wrapped and continued without any issues.
2015-06-25 16:28:04 +02:00
..
client.go rpc: implement provisioner update 2014-10-04 09:54:03 -07:00
client_test.go rpc: implement provisioner update 2014-10-04 09:54:03 -07:00
error.go
error_test.go
mux_broker.go Reverting a few lines from PR #2406 2015-06-25 16:28:04 +02:00
resource_provider.go core: close provider/provisioner connections 2015-06-19 21:52:50 +02:00
resource_provider_test.go core: close provider/provisioner connections 2015-06-19 21:52:50 +02:00
resource_provisioner.go core: close provider/provisioner connections 2015-06-19 21:52:50 +02:00
resource_provisioner_test.go core: close provider/provisioner connections 2015-06-19 21:52:50 +02:00
rpc.go rpc: Adding support for provisioners 2014-07-10 11:38:56 -07:00
rpc_test.go rpc: Speak new API with UIInput 2014-09-29 00:23:17 -07:00
server.go rpc: implement provisioner update 2014-10-04 09:54:03 -07:00
ui_input.go rpc: Speak new API with UIInput 2014-09-29 00:23:17 -07:00
ui_input_test.go rpc: Speak new API with UIInput 2014-09-29 00:23:17 -07:00
ui_output.go rpc: UIOutput 2014-10-04 09:11:51 -07:00
ui_output_test.go rpc: UIOutput 2014-10-04 09:11:51 -07:00