Hi @elsayedelmazon89 !
Great question, and we’d be happy to help you out here.
If you have a list of the SMB shares (no need to share them here, just wondering if you have them in a sheet or file) then we could probably pipe that to the vast cli quite easily. Are there ACLs that you want to apply as well, any other protocols etc?
If you could share an example of what the structure looks liks we can get started on providing you with some examples.
An example of what it could look like:
share_name,path,protocols,policy_id,alias,create_dir,tenant_id,qos_policy_id,enable_abe,abe_max_depth,description
finance_share,/shares/finance,SMB,1,/finance,TRUE,,,TRUE,3,"Finance department share with ABE enabled"
hr_documents,/shares/hr,SMB,1,/hr,TRUE,,,TRUE,2,"HR department share with limited ABE depth"
engineering,/shares/engineering,"NFS,SMB",2,/eng,TRUE,,,FALSE,,"Multi-protocol engineering share"
legal_archive,/shares/legal,SMB,1,/legal,TRUE,,5,TRUE,,"Legal documents archive"
marketing,/shares/marketing,SMB,1,/marketing,TRUE,,,TRUE,5,"Marketing share with deep ABE"
exec_share,/shares/executive,SMB,3,/exec,TRUE,2,,TRUE,1,"Executive share with dedicated tenant"
shared_projects,/shares/projects,"NFS,NFS4,SMB",1,/projects,TRUE,,,FALSE,,"Cross-platform project collaboration"
sales_team,/shares/sales,SMB,1,/sales,TRUE,,,TRUE,4,"Sales team collaborative share"
it_department,/shares/it,"NFS,SMB",2,/it,TRUE,,,FALSE,,"IT department multi-protocol access"
temp_projects,/shares/temp,SMB,1,/temp,TRUE,,,FALSE,,"Temporary project workspace"