You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.
Is your feature request related to a problem? Please describe.
Configuration files write livestream and video-on-demand resource properties, but do not support ivs resources yet.
Describe the solution you'd like
Similarly to the other resource types, write the IVS output URL to configuration files on each platform.
Possible JavaScript project configuration:
% cat src/aws-video-exports.js
// WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten.
const awsvideoconfig = {
"myinteractivestream": {
"aws_video_outputUrl": "https://###"
}
};export default awsvideoconfig;
A concern: it could potentially be difficult to tell when reading the JS config whether a resource is On-Demand or Interactive. As a result, it would be the responsibility of the user to know what their video resources are named.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem? Please describe.
Configuration files write
livestream
andvideo-on-demand
resource properties, but do not supportivs
resources yet.Describe the solution you'd like
Similarly to the other resource types, write the IVS output URL to configuration files on each platform.
Possible JavaScript project configuration:
Possible iOS/Android project configuration:
A concern: it could potentially be difficult to tell when reading the JS config whether a resource is On-Demand or Interactive. As a result, it would be the responsibility of the user to know what their video resources are named.
The text was updated successfully, but these errors were encountered: