NSFS | NC | CLI | Add force_md5_etag option to account and bucket schema/create/update

[romayalon]

Environment info

• NooBaa Version: VERSION
• Platform: Kubernetes 1.14.1 | minikube 1.1.1 | OpenShift 4.1 | other: specify

Actual behavior

1. Currently a user can not set force_md5_etag property to account/bucket.

Expected behavior

1. A user can not set force_md5_etag property to account/bucket.

Steps to reproduce

More information - Screenshots / Logs / Other output

[nimrod-becker]

Similar to what we have in regular deployments, add this option to an account config

[nimrod-becker]

Ref to usage in namespace_fs

noobaa-core/src/sdk/namespace_fs.js

Line 1607 in d1bf8c4

const md5_enabled = config.NSFS_CALCULATE_MD5 || (this.force_md5_etag ||

[shirady]

Hi,
I have an open question (also described in the PR comment).
If I have a general configuration with config.NSFS_CALCULATE_MD5 true.
Someone use the Manage NSFS CLI and decides that there is an account that will be a test account and creates it with --force_md5_etag false, what do we think that the value of md5_enabled should be?
Currently, the md5_enabled is still true.

cc: @romayalon @naveenpaul1 @nadavMiz

[nimrod-becker]

Specific Bucket/Account settings should override global settings

[shirady]

@nimrod-becker @nadavMiz it doesn't happen currently, do you want this change in the PR or a different one?
The current PR can be approved if we know it is a GAP to close (since it doesn't relate to the manage NSFS CLI).

[nadavMiz]

@shirady I will add this in this PR

[github-actions]

This issue had no activity for too long - it will now be labeled stale. Update it to prevent it from getting closed.

[shirady]

Closing, @nadavMiz fixed it in PR #7915.
Adding request validation label.
cc: @romayalon