awslabs / amplify-video

An open source Category Plugin for the AWS Amplify-CLI that makes it easy to deploy live and file based streaming video services and integrate them into your Amplify applications.
https://www.npmjs.com/package/amplify-category-video
Apache License 2.0
267 stars 56 forks source link

Need to have always S3 output bucket name even if CloudFront is activated #157

Open yudao opened 3 years ago

yudao commented 3 years ago

Is your feature request related to a problem? Please describe. When I want to remove my videos, I need to know the S3 output bucket name to perform a storage deletion. But if CloudFront is activated, we loose the bucket name. For now, I have a function to replace "input" string to "output" string on the input bucket name.

Describe the solution you'd like

// WARNING: DO NOT EDIT. This file is automatically generated by AWS Amplify. It will be overwritten.

const awsvideoconfig = {
    "awsInputVideo": "myvodstreams-prod-input-rl9bgpiw",
    "awsOutputVideo": "myvodstreams-prod-output-rl9bgpiw"
    "awsCDNVideo": "d221jzqmlju4ha.cloudfront.net"
    // or "awsOutputURLVideo": "d221jzqmlju4ha.cloudfront.net"
};

export default awsvideoconfig;

Describe alternatives you've considered No alternative solutions except my function to replace string that is for me non acceptable. We have to use the constants generated by the plugin.

Thanks for this great plugin.

Yu.

wizage commented 3 years ago

@yudao do you need the output bucket for deleting the assets? I.e. what you talked about in #158

Would you prefer #158 to be done or would you want both to be done? (This is easy just making sure we are doing a bandaid fix)

yudao commented 3 years ago

Hi @wizage!

Thanks for your reply.

Effectively, it's match with the delete issue #158 because I need it to delete in the right bucket. But I think that all created assets/services with dynamic env in name should be always accessible at any moment.

Thanks for this great plugin.

Yu.