CONSOLE-2508: Memsource automation

[rebeccaalpert]

Added one script to handle project creation, file generation, and file upload for Memsource and a second to handle download and file import into OpenShift.

I used https://github.com/unofficial-memsource/memsource-cli-client instead of the Ansible collection because I couldn't get the collection to work. We can always circle back and switch to that later.

Documentation is in the files themselves; installing the memsource cli client and providing credentials is required for use. One script also requires the rename utility.

I also made some revisions to the other scripts in our little tool chain here.

Fixes https://issues.redhat.com/projects/CONSOLE/issues/CONSOLE-2508.

[rebeccaalpert]

Updated PR to add the download script. Let me know if you have feedback. I also addressed the feedback on script #1.

[rebeccaalpert]

Just realized I didn't handle creating a new commit and PR in the script. I'll see if I can add that in.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dtaylor113, rebeccaalpert
To complete the pull request process, please assign jhadvig after the PR has been reviewed.
You can assign the PR to them by writing /assign @jhadvig in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dtaylor113]

Nice job @rebeccaalpert! Nice bit of scripting! :-)

[spadgett]

@rebeccaalpert A lot of variables are still missing quotes. Can you run shellcheck on the scripts and fix any errors? Thanks!

[openshift-ci-robot]

New changes are detected. LGTM label has been removed.

[rebeccaalpert]

Fixed the stuff shellcheck called out.

[spadgett]

Hey, @rebeccaalpert. There still seem to be warnings. Can you take another look? (Don't worry about the "not following" warnings.)

❯ shellcheck frontend/i18n-scripts/*.sh

In frontend/i18n-scripts/export-pos.sh line 5:
source ./i18n-scripts/languages.sh
       ^-------------------------^ SC1091: Not following: ./i18n-scripts/languages.sh was not specified as input (see shellcheck -x).


In frontend/i18n-scripts/export-pos.sh line 10:
  yarn i18n-to-po -f "$(basename "$f" .json)" -l $i
                                                 ^-- SC2086: Double quote to prevent globbing and word splitting.

Did you mean:
  yarn i18n-to-po -f "$(basename "$f" .json)" -l "$i"


In frontend/i18n-scripts/export-pos.sh line 18:
    for f in $d/locales/en/* ; do
             ^-- SC2231: Quote expansions in this for loop glob to prevent wordsplitting, e.g. "$dir"/*.txt .


In frontend/i18n-scripts/export-pos.sh line 21:
        yarn i18n-to-po -p "$d" -f "$(basename "$f" .json)" -l $i
                                                               ^-- SC2086: Double quote to prevent globbing and word splitting.

Did you mean:
        yarn i18n-to-po -p "$d" -f "$(basename "$f" .json)" -l "$i"


In frontend/i18n-scripts/languages.sh line 1:
LANGUAGES=( 'ja' 'zh-cn' 'ko')
^-- SC2148: Tips depend on target shell and yours is unknown. Add a shebang or a 'shell' directive.
^-------^ SC2034: LANGUAGES appears unused. Verify use (or export if used externally).


In frontend/i18n-scripts/memsource-download.sh line 5:
source ./i18n-scripts/languages.sh
       ^-------------------------^ SC1091: Not following: ./i18n-scripts/languages.sh was not specified as input (see shellcheck -x).


In frontend/i18n-scripts/memsource-upload.sh line 5:
source ./i18n-scripts/languages.sh
       ^-------------------------^ SC1091: Not following: ./i18n-scripts/languages.sh was not specified as input (see shellcheck -x).

For more information:
  https://www.shellcheck.net/wiki/SC2148 -- Tips depend on target shell and y...
  https://www.shellcheck.net/wiki/SC2034 -- LANGUAGES appears unused. Verify ...
  https://www.shellcheck.net/wiki/SC1091 -- Not following: ./i18n-scripts/lan...

[rebeccaalpert]

@spadgett - I'm not getting those anyway:

(.memsource) MacBook-Pro:frontend ralpert$ shellcheck -x i18n-scripts/memsource-download.sh
(.memsource) MacBook-Pro:frontend ralpert$ shellcheck -x i18n-scripts/memsource-upload.sh

[spadgett]

Honestly, I think it would be better to just avoid the special characters in the filename altogether, particular if Memsource does weird things with them. Then we can also avoid needing the rename utility. Would a convention like my-package__my-namespace be simpler? (Similar to BEM names.)

[rebeccaalpert]

I can make the change, but I'd have to rework two other scripts and we won't be able to download any older files with this system.

[spadgett]

I can make the change, but I'd have to rework two other scripts.

I think it's worth doing.

[rebeccaalpert]

Addressed feedback. I adjusted naming scheme in a separate commit so we can drop it if needed. Note that this change will prevent us from using any of the scripts for dealing with translation files that we've already sent over under the original naming scheme (we have one batch currently in process).

[spadgett]

Thanks @rebeccaalpert

[rebeccaalpert]

All set.

[rebeccaalpert]

@spadgett; I squashed; let me know if this is good to go or if you have additional feedback. I used it to upload Sprint 200, but Sprint 199 will be in the old format and we'll have to revert the tools to the old naming scheme locally to import those.

[spadgett]

/lgtm

Thanks @rebeccaalpert.

[spadgett]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dtaylor113, rebeccaalpert, spadgett

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• frontend/OWNERS [spadgett]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment