Vault and File System Attributes

[gph]

Hi,

I'm running Vault Client and Server 2.0.2

I would like to highlight a small annoyance with Vault and file system attributes. By default, Vault uses the Read-Only attribute to lock files that are checked in and clears the attribute when checked out - an acceptable technique for version control.

My annoyance is that when I check a file out (or get latest), in addition to clearing the Read-Only attribute and setting the Archive attribute (both as expected), Vault also resets the Hidden attribute (from Hidden to Visible). I suspect that this is also the case with the System attribute.

I appreciate that Vault does not store attributes, however, it should not change 'other' file system attributes unnecessarily. In our case, we use the Hidden attribute to control our development/beta/production migration scripts and I'm sure other developers use the Hidden and System attributes for other purposes.

Would it be possible in a future version of Vault, that files involved in a check out or get latest operation first check the destination Hidden & System attributes, and leave them unmodified? If performance is an issue, perhaps add a check out / get latest option that asks how to handle attributes?


Regards,

Grant Henderson

[dan]

That's a fair complaint - we'll add it to the list.

Thanks,