-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assets plugin ideas #281
Comments
Upload multiple assetsIt might be useful to be able to upload and deploy multiple assets at the same time. If a |
Download AssetsThere is no This could especially be powerful if it would support a twilio assets:download *.mp3 Bonus if it detects twilio assets:download index.html | grep h1
# or
twilio assets:download index.html > backup.html Support for Name propertyThe name on your hard drive might contain sensitive information. It would be great to pass Dynamic Upload from StreamRather than only supporting uploading files that are coming straight from your hard-drive it could be useful to upload things that are being passed in via the wget https://demo.twilio.com/docs/classic.mp3 | twilio assets:upload --name special-song.mp3 |
I see that the issue i logged is covered in here - downloading assets is still not a thing. even on the roadmap? |
Currently it's not possible to create backups of twilio services without downloading protected-assets. Would love the feature to download protected assets. |
This issue is a bucket of ideas for the Assets plugin as I think of them. Please add other ideas.
Asset permissions
Initially all assets are uploaded as public. I can see an argument for creating protected assets (audio files for use during calls, for example). Could do this with a flag
twilio assets:upload file.ext --protected
. I can't see a reason you would want a private asset in a service that only has assets.Asset deletion
This can be done with the Twilio CLI using the service SID and asset SID, but we could make it easier.
Service deletion
This can be done with the CLI too, but that would not remove the SID from the plugin config. This should come with a serious confirmation step to ensure that is definitely what the user intends.
The text was updated successfully, but these errors were encountered: