Uploaded image for project: 'Razor'
  1. Razor
  2. RAZOR-940

Metadata update does not throw error around no_replace

    XMLWordPrintable

Details

    • Hide

      Run `update-node-metadata` and `modify-node-metadata` using `no-replace` == true on a key that already exists on the node and see an error returned. In `modify-node-metadata`, pass `force` == true to suppress the error and notice the key is not updated.

      Show
      Run `update-node-metadata` and `modify-node-metadata` using `no-replace` == true on a key that already exists on the node and see an error returned. In `modify-node-metadata`, pass `force` == true to suppress the error and notice the key is not updated.
    • Analytics
    • 1
    • Analytics 2016-10-19

    Description

      When the user runs either modify-node-metadata or update-node-metadata using the no_replace flag, the result is that the operation fails silently for any key(s) that already exist. This is not the behavior documented for these commands, which state that the command will fail if this happens.

      In the case of modify-node-metadata, a new flag force will be added so that batch operations can still succeed. This will allow feature parity with the existing behavior by supplying a value of true.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              scott.mcclellan Scott McClellan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support