Populate from ASpace button - select list is not populated in production

[eporter23]

When deploying the latest Curate version to production, the ASpace integration is visible in the New Collection form, but the popup window does not populate any values in the initial repository select list menu.

[eporter23]

@abelemlih this is now in production, but do you know if additional work is needed for this integration or is this a bug?

[bwatson78]

This was due to two factors:

1. The needed RAILS_ENVs were not in place. They now live in .env.production.
2. The ip address 52.207.83.54 was not whitelisted to communicate with our production ArchivesSpace. That has been corrected as well.

I have observed that the ArchivesSpace collections show in that pulldown's options.

[eporter23]

@kmichaelis this should be ready for testing, if you have a new collection to setup?

[kmichaelis]

The list previously appeared populated but no longer does.

[bwatson78]

PR made: #2230

[eporter23]

@kmichaelis and @bwatson78 I created a new collection in both arch and test via the Import from ASpace option. @kmichaelis do you want to/have you already done further testing, or is this okay to go to production?

[bwatson78]

After working without error in Test and Arch, choosing to create a new collection produces a 500 with the following error:
ArchivesSpace::ConnectionError (API client login failed as user [curate_api], check username and password are correct)

I asked @erussey if this could be a whitelisting issue, she agreed and advised me to email as@lyrasis.org for further assistance. I will add a comment when I receive word back from them.

[bwatson78]

[bwatson78]