You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you create an export policy with a rule that does not have the nfsv3 or nfsv41 block then the export policy does not get created. Instead there should be an error stating that one of them are required.
The text was updated successfully, but these errors were encountered:
The behaviour mirrors what the UI does. Without either "ticking" NFSv3 or NFSv4, the export rule is invalid. Without any valid export rule, no export policy is created.
What happens here is, that we pass the (invalid) export rule to the API and the API silently ignores it. The UI - in contrast - throws an error telling the user what is wrong. See picture.
While this "works as designed", one could argue that the API or the TF provider could be more user friendly and return an error ...
If you create an export policy with a rule that does not have the nfsv3 or nfsv41 block then the export policy does not get created. Instead there should be an error stating that one of them are required.
The text was updated successfully, but these errors were encountered: