Sam Patzer

Should be completed in #1

We have considered this, problem is we have a dependencies on Secrets Manager (Not supported with Functions), Amplify CLI doesn't support in order spinning up resources and since some of...

After our discussion on this we are trying to decide the best method/path to go down. Few options are being considered: 1) Trigger the Lambda function when the MediaConvert job...

Do you mind sharing your schema here from the Amplify CLI so we can take a look at what you are currently using? Thanks, Sam Patzer

Ahhh this is a bug! For right now, you can manually add it: ``` #DO NOT EDIT type videoObject @model @auth( rules: [ {allow: owner, ownerField: "owner", operations: [create, update,...

Fix is easy enough to push forward and do! I will take a stab and put in on a beta branch for you asap :)

Beta is published here: `npm i [email protected] -g` Steps to move to this new version: 1. Remove `videoObject` and `videoAsset` from your schema file. 1. Run `amplify video update` and...

Hmmmmm sounds like you didn't save the graphql or edited the wrong file. Make sure you are modifying this exact file: `C:\VueJS\wbs-platform\amplify\backend\api\wbsplatform\schema.graphql` Remove the entire type for both videoObject and...

Hey @tscole In your Element you still reference `vodAsset: vodAsset @connection` We do a search for any vodAsset or vodObject as to not collide with your schema. You can either...

Thanks @yudao for the feature request. I am curious, we been looking at storing the state of the transcode job to the DynamoDB table, and then use appsync subscriptions to...