idemixgen was using the orderer metadata so
added a metadata sub package

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

use pathto to keep links relative

Change-Id: Id60c9702630dbd83d256166db31257f05890a91c
Signed-off-by: Dohyeon Kim <nero.union12@gmail.com>
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
(cherry picked from commit 6238d584ca9a9f1f1d41b547895a43decf26e9f4)

Change-Id: I000c4fbeb0c2949d8fe2680370cef5797af380f6
Signed-off-by: Artem Barger <bartem@il.ibm.com>

Updating help text for
peer channel create command
indicating that the channel name
must be all lower case

Change-Id: I3c5520d57ea3ab3f4576e04f77e49bb22e9ad33a
Signed-off-by: pama-ibm <pama@ibm.com>

Also, reorder the elements in configtx.yaml for logical consistency with
the config model.

Change-Id: I54d4387c890cdfea708c0a74435bc38d5cf203b1
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

The validation test has a sample implementation of a validation plugin.
There is a missing call to Done() in the code.
Since this is just a test, it doesn't affect production runtime,
but it might still serve as a reference of how to write a validation plugin.

Therefore, to set a good example - we should also add a call to Done()
on the state object after we obtain it.

Change-Id: Ie96a8fdf583aa2c8c64ceb119810bb1764ba3041
Signed-off-by: yacovm <yacovm@il.ibm.com>

Most of the configtx.yaml documents in the tree contained invalid YAML.
This wasn't detected before now because bugs in go-yaml have hidden the
issue. These changes need to be made before the parser is bumped to help
ensure things don't break.

A draft release note has been added to the tree to highlight the issue
as we approach the end of our current release cycle.

Change-Id: I8d9cd9e2278ccd51ffd136fd17e3d858f6b56b2d
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

The identity mixer based MSP now supports anonymity principals
and combined principals.

Change-Id: Ib703d47d8729e697c351379d64da67bd022a5b34
Signed-off-by: Manu Drijvers <mdr@zurich.ibm.com>

This change set adds support for cc2cc queries for the discovery service.

Change-Id: I08707c906d7f0da7b38ded55f8f5a5b31a7e50aa
Signed-off-by: yacovm <yacovm@il.ibm.com>

There is a missing call to Close() after obtaining the RWSetScanner
and iterating over the results, in the private data support
for the endorser plugins.

Change-Id: I645ae82f2e985188b1d526461695aaf24a77674e
Signed-off-by: yacovm <yacovm@il.ibm.com>

The endorser's private data support assumes there is simulation
results if the iterator claims the iteration hasn't ended and
if there aren't any - it returns an error.

I think it's better be safe than sorry and just skip this iteration
and continue to the next one, and in the worst case - the user
anyway needs to inspect the results from this method.

Change-Id: I765057f6f4d231eceef55232b3831f5925a17dfa
Signed-off-by: yacovm <yacovm@il.ibm.com>

To avoid scope creep, 
please only comment on the
following entries in the
glossary:
- Added ACL
- Updated Policy, Anchor Peer
Leading Peer

Change-Id: I14cc55b180120522900914b4193095fbc6be8f50
Signed-off-by: pama-ibm <pama@ibm.com>

Change-Id: I979b8ffbe69b87bf2e93613e4357ba8356f7f037
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

Java shim expect private key in PKCS#8 format, so now peer store it
required way.

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

Tell peer channel create to write the genesis block to /dev/null.

Change-Id: I7d2e6c00dde1bf86a3c49234f89503e43ab3c6b7
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

By default, peer channel create will create a file in the current
directory named $CHANNEL.block. If a different output file is desired,
the --outputBlock flag can be used to specify the path.

Change-Id: I8b0f2ced26c62a21e3139688c588c10763ed533c
Signed-off-by: Matthew Sykes <sykesmat@us.ibm.com>

The "peer channel fetch" and "peer chaincode install" commands
currently log their success output message at the debug level.
This can make certain integration/e2e tests fail unexpectedly
if the log level is set to any other level.

It seems natural that the logged success message should be at
the info level.

Change-Id: I8ad961a5b55b7a353f329218d9090457ed1bf0be
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>