I've seen several articles and post on this subject, but most of it seems maybe outdated or maybe I have the wrong version.
This article seemed to be what I needed, but CopyBlobHelpers.CopyBlobAsync does NOT seem to be supported.
https://learn.microsoft.com/en-us/azure/media-services/media-services-copying-existing-blob
I think what I need is simple:
Take a file/blob from an Azure Storage account and "copy" to Media Services as an Asset so that it could then be encoded.
thanks,
v.
I just updated the sample on github
https://github.com/Azure-Samples/media-services-dotnet-copy-blob-into-asset
and the article will also be updated tomorrow.
Let me know if you have issues with the code.
thank you,
Julia
Related
I can't seem to find any documentation for uploading and encoding on the microsoft docs for AMS. All I see is live stuff. I do see this on the dotnet SDK, but not for node.js, so I'm trying to find something using the REST API. Does anyone have any microsoft docs or tutorials for uploading and encoding Azure Media Services v3 using the REST API?
Thanks for any help (I'm a newbie here)
For REST see the following: https://learn.microsoft.com/en-us/azure/media-services/latest/stream-files-tutorial-with-rest
For Node.js see the following: https://learn.microsoft.com/en-us/azure/media-services/latest/stream-files-nodejs-quickstart
We are adding more and more Node.js content now that the newer Typescript SDK is out there.
Keep an eye on samples here.
I built a simple upload and encode sample here.
https://github.com/Azure-Samples/media-services-v3-node-tutorials/tree/main/AMSv3Samples/StreamFilesSample
Let me know if that gets you started and if that is enough information to understand the basics.
I would avoid trying to roll your own REST based SDK client, since there is very helpful retry logic built into the official NOde.js/TypeScript SDK for Media Services.
Recently i have discovered that ability to change to Classic Experience of Azure Function portal is not there right now. I have used some functions that has been created in old Power Shell module and since that i had to create it with Experimental Language.
Is there any others experiencing same issue as mine. Please help me on this.
Are you attempting to create a new function or view old ones? I'm in a similar position, and found an older work around for calling PnP from site script via .NET. MS docs still reference the method you are talking about, though.
https://learn.microsoft.com/en-us/sharepoint/dev/declarative-customization/site-design-pnp-provisioning#create-the-azure-function
https://www.sharepointnutsandbolts.com/2019/01/Site-Designs-PnP-Part1.html
Found some additional documentation here!
https://github.com/SharePoint/sp-dev-docs/blob/master/docs/declarative-customization/site-design-pnp-provisioning.md
Last date edited was 07/04/2020.
The new portal experience of Azure functions became general this year.
You can check out this YouTube video published my Microsoft about the "How to" of this experience: https://www.youtube.com/watch?v=0bdT_9uOqkg
If you don't want this view, you can Switch to classic experience.
Obviously Stack Overflow is not the place for this question, but twitter #azuresupport refuses to do anything other than tell people to post here with a tag. So here goes.
Where the #$%# are the node sdk docs? They used to be in google cache, and now they aren't even there. There are multiple issues in the github asking for the docs.
https://github.com/Azure/azure-sdk-for-node/issues/2291
The Internet Archive still has a cached copy at https://web.archive.org/web/20170107075814/https://azure.github.io/azure-sdk-for-node/azure-sb/latest/global.html
The docs were inadvertently removed from the doc repo, and we are working to resurrect them. We're sorry about that and will comment here when they're back.
Thank you for your patience,
Karl
For those who've already migrated from Parse's Cloud Code to Azure's Mobile Services or those who have a good enough grasp of both to know how this would be done: Can you outline the high-level steps for migrating off of Parse and into Azure?
My concerns:
Parse has an excellent ACL system but I wonder if there are scripts to translate it into Azure's DBs and tables.
I wonder what's a close mock-equivalent of Parse's JS SDK so that I could Simply swap out Parse.. with Azure.. and still have code running seamlessly.
Is this a pipe-dream?
Parse enables you to export files in a JSON format. You will find this feature under the Settings tab for your Parse app.
Since the announcement of the Parse shutdown, Microsoft has posted guidance on migrating from Parse here: https://azure.microsoft.com/en-us/blog/azure-welcomes-parse-developers/
Perhaps a bit too late for the OP but hope it helps.
Background: My idea is to create a primarily content-heavy website (think news articles or blog posts) written entirely in nodejs. Since creating content on Google Drive (Google Docs) in particular is very simple, what I would like to do is have Nodejs retrieve the website's content from Google Docs.
Challenge: As far as I can tell, the correct way to do this according to Google is to create a Service Account so that the application can access the files stored on Google Drive without requiring user-intervention in the form of a confirmation. Google provides three libraries--java, python, and php--for server-to-server requests. Does anyone know of anything similar already written by the Node community? I am aware of node-oauth but I've searched through it's source and haven't found anything referencing private keys, which are required for server-to-server interaction, which I'm taking to mean it's not supported. Writing one is also an option, but I'd like to avoid that if at all possible. Looking at the Google-written Java Oauth2 client library makes it pretty clear that it's not an easy task.
Thanks in advance!
This is one library I've found that looks pretty thorough and complete for creating JSON Web Tokens: JWCrypto
I know this thread is old, but in the event others arrive here looking for an answer:
Google is working on an official module to access all of their API's. Its alpha so be careful but it looks very nice- github repository