Specifying leading directories in path to template files causes parsing errors

[mattmendick]

I created an issue on Cortex (cortexproject/cortex#3357) about weird directory processing behavior on the alertmanager side, but @gotjosh suggested I create an issue here to address the root problem. I wouldn't assume the path that I'm asking cortextool to read it from on the local machine would have any effect on how cortex processes the file on the backend. I'm not sure the path should be sent to the backend. Even the filename is kind of annoying to have to be sent, but to match up the template name with the alert yaml I think that is necessary.

This seems like an issue where the tool should ignore the directory specified and not send that full path to the backend.

[Carmezim]

@mattmendick I got that same error but given cortex is trying to create a temp file for validation on /tmp and on recent MacOS's the write access to root has been revoked by default.

Is there a way to define the path for the validation yaml when loading alertmanager configs?