User story: As a user of cloudelastic, I want the Commons File index to be up to date so I have access to accurate & timely data.

Commons has the usual indexes—content, general, and archive—plus a file index, which other wikis do not have. The reindexing process handles them in a fixed order: content, general, archive, file.

The Cloudelastic environment is not private, so the archive index is not created. It appears that this is reported as an "error", which stops the reindexing process, so no attempt is made to update the file index.

1. A somewhat kludgy approach would be to move the logic that adds the file index to the list for Commons ahead of the archive index.
2. A better approch would be to allow the archive index to "fail successfully" on Cloudelastic, so the file index can continue.
3. Another alternative might be to be smarter about knowing what indexes are allowed where and not trying to index archive on Cloudelastic, but that could be brittle in the long term.

Acceptance Criteria: Reindexing Commons on the Cloudelastic cluster at least makes an attempt to update the File index (it may fail for other reasons, as they do).