[Bug] Exporting alerts with wrong alert name

[phospi]

Hi there,

I'm using cfme-rhconsulting-scripts to export cfme alerts. I observed that for every cloudforms alert there is a file created where the filename == alertname. In cloudforms it is perfectly fine to use every available unicode or special character to name the alert. However, when exporting such an alert name as a filename things become awkward. I know that UNIX-based filesystems are less bitchy about special characters. AFAIK, it is a best practice to avoid special characters in filenames. I guess that a lot of problems can arise from just copying any character in a filename without escaping special characters.

Issue 1:
I just tested that I can create alerts with 300 characters. As you might know, the maximum length for a file name is about 250 characters. Such alerts currently raise an OS error as you can see here:
Errno::ENAMETOOLONG: File name too long @ rb_sysopen - /opt/git/cf-region96/cloudforms/MIQEXPORT/alerts/abcdoflkgndaslgndflskgnlgnregklmgknrkmgrkdfadflnafaidnsflasfjoewrjpaewmffklmöasfokaewrkdklgmvdvdmksflanofeawfmwpmfsolamfdsklfnkglw4eirnflaeiwnflawnfkawöolmfoö3ewmfkoaewöfmewolgnfklgneiwkgneiwrnfewnfewlianflasnflknaewflnaweflvnlwaenvlaewnflaewnglaewnflaewn.yaml

Issue 2:
We just had the issue that we exported an alert with the following special characters: ":<>%". When exporting this into git there was no issue but importing it again into a windows machine broke the git repository because the file name was truncated after ":".

I can't tell exactly where address this issue? Do you have to change your export script or is this something that has to be addressed directly to the cloudforms developers?

Kind Regards,
phospi