We bump the vagrant devenv from 0.0.10 to 0.0.11 to pick
up the latest protoc binary.  Users will need to vagrant
destroy+up to work with this code.

This has been tested with a full unit-test/behave cycle
in both Jenkins and vagrant (after a destroy/up cycle).

https://jira.hyperledger.org/browse/FAB-108



Change-Id: I62bc7925379a7db86b58aa6cca5ddaeb1069456d
Signed-off-by: Yacov Manevich <yacovm@il.ibm.com>
Signed-off-by: Gregory Haskins <gregory.haskins@gmail.com>

This commit makes it possible to pass in a JSON string
containing Args and Function keys or just Args key as
a chaincode input object for chaincode operations.

Change-Id: I46fefc1eff0de169b0c5efbedbdea038e8cc9d3e
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Change-Id: I7b34fb707a26e07b77df3e2067adbce41fd666d5
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Change-Id: Ifcda6ce5f3ec4714fea17519bd041343e4461751
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>

This will fix issue FAB-215
https://jira.hyperledger.org/browse/FAB-215



Change-Id: I2599ba09f81ae44f9e6f28b53917300d2922a897
Signed-off-by: Satheesh Kathamuthu <satheesh.ceg@gmail.com>

To simplify the usage of mapping between the docker-compose service
to container name mapping add a dictionary mapping the service (or
alias) to the container data object. Also add a map of full container
name to container data object for convenience.

Standardize the naming of a compose service to containerAlias to
reduce confusion between the actual containerName and the service
defined in docker-compose.
e.g. I deploy chaincode "{chaincodePath}" with ctor "{ctor}" to
     "{containerAlias}"
containerAlias could refer to "vp0" when in reality the container is
called "bddtests_vp0_1"

Rename the ContainerData class to Container and its field:
containerName to name to reduce verbosity in the code base.

Remove functions that were no longer used afer changing the code to
use the map of alias->container.

Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>
Change-Id: I870719f3ff4db9d07f23d61f1d1a411b6e7ad804

Prior to this fix, it was possible to add duplicate peers
to the chain.  This fix now adds check to the addPeer method
and throws a DuplicatePeer error if a peer with the same URL is
already a member of the chain.  Also added a test for adding multiple
valid peers to the chain

Fixes FAB-264

Change-Id: I575200325bf8e8aedc72e1f41419099689c3a6fc
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

Add missing parentheses in HFC sample.

Change-Id: I2cd54231e86eaa8861bf13b536119de9716a5352
Signed-off-by: Nao Nishijima <nao.nishijima@hal.hitachi.com>

In docker-compose-1-empty.yml nc was being invoked directly which led
to SIGTERM being ignored by the container. This added an unneccessary
10 second wait after tests that used it while docker timed out and
sends a SIGKILL. This fixes that by forking nc and trapping SIGTERM
and directly killing nc.

Change-Id: Ifc5072b33c45f9fa90868a87ca69982c051e10e1
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

Current JDK image sourced from dockerhub (java:openjdk-8) is being
deprecated (see https://hub.docker.com/_/java/

). Update the relevent
docker file to use the new openjdk:8 image.

Change-Id: Idf9bac8ac6f981ea6e0311190365f37f98915666
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

The `peer network login` command does not specify that it
requires a username argument:

$ peer network login
Error: Must supply username
Usage:
  peer network login [flags]

This change modifies the usage message to:

Usage:
  peer network login <username> [flags]

Change-Id: I7ffbc312a9ee33ba34584c4cb57d091ffeb4b2dc
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>

When attempting to deploy with the peer CLI, if the user has not
logged in they get the error "User x not logged in. Use the
'login' command to obtain a security token."

It took me a couple of minutes to figure out what the 'login'
command actually is. I feel the error should specify it as
'peer network login'.

I think this error is specific to the `peer` CLI code,
so it should not affect REST or the Node SDK.

Change-Id: I3d6d4e748d9dbf543c50c2754ef21cacfa14a069
Signed-off-by: Bradley Gorman <bgorman@au1.ibm.com>

The name of the field UUID was also changed to TxID.

Change-Id: Iedeed9af13a99671a756c32944a8c6814d4b2b20
Signed-off-by: Gabor Hosszu <gabor@digitalasset.com>

Change print() statements to bdd_log(), defined in bdd_test_util.py
This change provides a manner for keeping all log statements in the
same format. Currently this format is simply the current time
followed by the speicified message.

Also added the copyright header to sdk_impl.py and removed unused
imports.

Change-Id: I87590bbcd6512eefcce46dc9e7f854597c203b17
Signed-off-by: Julian Carrivick <cjulian@au1.ibm.com>

Remove deprecated devops API. Skipped one behave test that still used
it. Will open separate issue to deal with that. Update API docs.

Fixes FAB-258

rebased

Change-Id: Iba55fb271aca5a1d1d8e895ecc6ff34c69f59ac2
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

TestHTTPExecuteDeployTransaction is failing on master
because it is trying to go get
http://github.com/hyperledger/fabric-test-resources/examples/chaincode/go/chaincode_example01


which implements new interfaces from the convergence branch.
This patch points the test at a different repo for now and demonstrates usage of
gopkg.in to attempt to overcome limitations of go versioning

Fixes FAB-305

Change-Id: I55113b36a7cd6c505e7dc2503a31d91fa11b8c5b
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

Change-Id: I1b840d303674b7469d537aa3f70a87530f757b06
Signed-off-by: Srirama Sharma <sriramsh@in.ibm.com>