Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace config validation #833

Merged
merged 3 commits into from
May 26, 2022
Merged

Commits on May 24, 2022

  1. validate namespace configuration

     * `name` must be unique on this node
     * for historical reasons, "ff_system" is a reserved string and cannot be used as a `name` or `remoteName`
     * a `database` plugin is required for every namespace
     * if `mode: multiparty` is specified, plugins _must_ include one each of `blockchain`,
      `dataexchange`, and `sharedstorage`
     * if `mode: gateway` is speicified, plugins _must not_ include `dataexchange` or `sharedstorage`
     * at most one of each type of plugin is allowed per namespace, except for tokens (which
      may have many per namespace)
    
    Signed-off-by: Alex Shorsher <alex.shorsher@kaleido.io>
    shorsher committed May 24, 2022
    Configuration menu
    Copy the full SHA
    10f8b9e View commit details
    Browse the repository at this point in the history

Commits on May 26, 2022

  1. Enforce unique plugin names

     - Plugins names must be globally unique
     - Better handling of deprecated config in namespace manager
     - Updated config descriptions
    
    Signed-off-by: Alex Shorsher <alex.shorsher@kaleido.io>
    shorsher committed May 26, 2022
    Configuration menu
    Copy the full SHA
    e41e51b View commit details
    Browse the repository at this point in the history
  2. upgrade ff-common to 0.1.6

    Signed-off-by: Alex Shorsher <alex.shorsher@kaleido.io>
    shorsher committed May 26, 2022
    Configuration menu
    Copy the full SHA
    b7b389e View commit details
    Browse the repository at this point in the history