anchor.diff:          "provider": null,
           "syslog\_drain\_url": null,
           "tags": [
  -        "nfs"
  +          "nfs"
           ],
           "volume\_mounts": [
             {
  
positive.code:   * For NFSv4,  specify a `version` parameter in the create configuration.
    * For read-only mounts, the driver enables attribute caching. This results in fewer attribute RPCs and better performance.
    * When you omit `uid` and `gid` or `username` and `password` in bind configuration, the driver skips `mapfs` mounting and performs just the normal kernel mount of the NFS file system without the overhead associated with FUSE mounts.
  * `nfs-legacy` (deprecated): This volume service is implemented with libfuse. It does not support
  `version` parameters and only mounts NFSv3. The service also has some performance constraints.
  
  Both services offer a single plan called `Existing`.
  
  
negative.code: 
  With the release of NFS Volume Service 1.5.4, the original fuse-based NFS service has been deprecated in favor of the newer kernel-mount based NFS service and will eventually be removed.  Existing NFS volume service bindings will now be listed as `nfs-legacy`.  To switch over from `nfs-legacy` to the newer `nfs` service, we recommend that you re-create and re-bind your `nfs` service instances.
  
  With the release of NFS Volume Service 2.0.0, the `nfs-legacy` service has been rewritten to use the `nfs` service behind the scenes.  We still recommend that you re-create and re-bind your `nfs` service instances to avoid being affected when the `nfs-legacy` service is eventually retired.
  
  ### <a id='nfs-sample'></a> Deploy and Bind a Sample App
  
  