| In PUP-10255 we added the ability to readlink symlinks within the environmentpath. This causes resources to report the full non-symlinked path as their location in the catalog and report. Now, when using versioned dirs, whenever a new code deployment happens that full path changes (because it contains the environment version in the path). This causes a lot of unnecessary churn in catalogs and reports because even unchanged resources look like they come from a different path. We should enable the ability for a resource to report itself as coming from the symlinked path rather than the full path after readlinking. This ability should be behind a configuration flag and default to off. NB. This maybe be possible by editing how the source locator in the parser reports what file a resource it created came from. Though, if resources take that file information and try to access the disk themselves (eg, in a create_resources like step) then we may not be able to do so. Another route may be to post process the catalog and adjust the every resource to use the original symlinked env path. |
