Update staging to use the test connection stream dams4-test-securetoken.

[lsitu]

Local Checklist

• Tests written and passing locally?
• Code style checked?
• QA-ed locally?
• Rebased with master branch?
• Configuration updated (if needed)?
• Documentation updated (if needed)?

What does this PR do?

Update staging to use the test connection stream dams4-test-securetoken to stream from staging environment.

Why are we doing this? Any context of related work?

@remerjohnson reported that the video object he ingested (https://librarytest.ucsd.edu/dc/object/bd9167310g) is streaming with "404 Not Found" error. And Ron created stream connection dams4-test-securetoken to stream from the staging localStore.

Deployment Instructions

Deploy to staging for test.

@ucsdlib/developers, @rstanonik - please review

[rstanonik]

QA, Staging, and Production have separate localStores (Isilon shares) for DAMS data. Wowza has separate connection URLs to stream data from the Staging and Production localStores (dams4-securetoken and dams4-test-securetoken), so the Staging and Production environments must use the matching streaming URL, especially for testing ingestion. Currently there is no Wowza connection URL for QA. Let me know if you need one.

[lsitu]

@rstanonik Thanks. Could we have the connection streaming for QA as well?

[rstanonik]

I created a similar Wowza connection url for QA dams4-qa-securetoken.

[rstanonik]

Here are simple examples demonstrating each

https://aal.ucsd.edu/tchu/dams4-securetoken/

https://aal.ucsd.edu/tchu/dams4-test-securetoken/

https://aal.ucsd.edu/tchu/dams4-qa-securetoken/

They are in aal because I was working with Vivian on something at the time.

[rstanonik]

If it is useful to keep the examples around, I'll find someplace more suitable.

[lsitu]

That sounds nice. Thanks @rstanonik. I've updated the QA environment to use dams4-qa-securetoken as well (see commit 2677389).

[lsitu]

@hweng Could you review and merge it if you get a chance. We need to fix it on staging so that it won't delay @remerjohnson's ingest process. Thanks.

[coveralls]

Coverage remained the same at 65.98% when pulling 2677389 on feature/test_connection_stream into fdb14d0 on develop.