[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jir... ] Fabian Deutsch edited comment on OVIRT-1047 at 2/13/17 1:28 PM: ---------------------------------------------------------------- You know - I don't disagree - if I was reading the ticket (as a 3rd person), then I'd say it's silly as well - to just discuss names. But to be a good citizen, I'd say an ovirtci file would make sense. [~eedri] the .ovirtci file could -in the easiest case - effectively have the same structure as the dir, it would just be fields in the yaml file. {code} toYaml() { for F in automation/*; do echo $F: |" ; sed "s/^/ /" < $F ; echo -e "\n---" done echo } $ toYaml > .ovirtci {code} and back {code} fromYaml() { sed -e "s/^automation/cat <<EOF > automation/ ; s/---/EOF/ ; s/: |// ; s/^ //" } $ fromYaml < .ovirtci {code} And from there it could be gracefully improved - if wanted. was (Author: fdeutsch): You know - I don't disagree - if I was reading the ticket, then I'd say it's silly as well - to just discuss names. But to be a good citizen, I'd say an ovirtci file would make sense. [~eedri] the .ovirtci file could -in the easiest case - effectively have the same structure as the dir, it would just be fields in the yaml file. {code} toYaml() { for F in automation/*; do echo $F: |" ; sed "s/^/ /" < $F ; echo -e "\n---" done echo } $ toYaml > .ovirtci {code} and back {code} fromYaml() { sed -e "s/^automation/cat <<EOF > automation/ ; s/---/EOF/ ; s/: |// ; s/^ //" } $ fromYaml < .ovirtci {code} And from there it could be gracefully improved - if wanted. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)