How to change Media Reserved Unit type & count in the V3 API?
Can currently be changed from V2, however I don't see anything about reserved units in the api?
V2 Version
CloudMediaContext AzureContext;
var reservedUnit = AzureContext.EncodingReservedUnits.FirstOrDefault();
reservedUnit.ReservedUnitType = reservedUnitType;
reservedUnit.CurrentReservedUnits = units;
reservedUnit.Update();
Reference
https://learn.microsoft.com/en-us/azure/media-services/previous/media-services-scale-media-processing-overview
https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.management.media.azuremediaservicesclient?view=azure-dotnet
azure media services v3 - how to change Media Reserved Unit type & count?
Unfortunately, it is not supported in the Azure media service v3 currently. Media Reserved Units can only be managed using the Media Services v2 API. It is a known issue.
For more information about changes that were introduced in Azure Media Services (AMS) v3, shows differences between two versions, and provides the migration guidance, please refer to Migration guidance for moving from Media Services v2 to v3.
Known issues
Currently, you cannot use the Azure portal to manage v3 resources. Use the REST API, CLI, or one of the supported SDKs.
Today, Media Reserved Units can only be managed using the Media Services v2 API. For more information, see Scaling media processing.
Media Services entities created with the v3 API cannot be managed by the v2 API.
It is not recommended to manage entities that were created with v2 APIs via the v3 APIs. Following are examples of the differences that make the entities in two versions incompatible:
Related
The REST API I am thinking about is the one of cloud accounting software Exact Online. I am trying to set this up just using Google Cloud Platform tools.
I am currently on Google Analytics API v3. Since Google Analytics 4 (GA4) just came out, I am looking into upgrading to API v4, however, I have noticed that the API v4 does not include GA4 properties and the API that handles GA4 properties is currently in alpha (I believe it's Data Reporting v1).
Will it be more work for me to update my existing application to API v4 from v3, and then when the beta or general release for the Data Reporting v1 arrives, upgrade then, or should I wait to upgrade from API v3 to
I am under the impression that v4 doesn't have the ability to pull GA4 properties, however, since it runs on completely new endpoints and Google has mentioned all future development will be on v4 then I should just move to it so its less work when the newest API comes out with those features. Does that sound right?
Marshall,
You are correct, the Google Analytics Reporting API V4 cannot access GA4 properties, you need to use the Google Analytics Data API V1 in order to do this. New features development will only be done in the Data API. Both APIs are conceptually similar, but the decision mostly depends on which type of properties you need to access.
As a side note, I believe the Data API is slated to graduate to Beta in a matter of weeks.
Thanks,
Ilya
The Google Analytics Team
A POC in our project uses IBM Watson Discovery services hosted in cloud for natural language analysis but our company wants an on premise solution for natural language analysis instead of cloud based one.
Is it possible to replace IBM Watson discovery API completely with IBM Watson Explorer.
I did some research and found that Explorer does not have Node JS APIs.
Also IBM Watson Explorer Rest API can be used for simpler use cases like searching.
Please help me in this regard as my knowledge on these two tools is limited.
To answer your question in short, yes it can be done.
Watson Explorer does have an API interface and yes it can be integrated with Node JS as well, it does not have a native npm package...I personally have implemented a very complex solution for a very reputed an automotive client using WEX as the Backend and Data Ingestion engine and Node JS on top, acting as the orchestrator and the UI.
You may want to see this post: https://developer.ibm.com/answers/questions/259089/rest-apis-for-wex-search/
> On Linux: {hostname}/vivisimo/cgi-bin/velocity?v.app=api-run
> Windows : {Hostname }/vivisimo/cgi-bin/velocity.exe?v.app=api-run
The api-runner have all the api's listed and one can also test them against the search collections (search collections are the equivalent to a table where the data is ingested and there are a lot of custom configurations which can be applied to make use of, for advance use).
So for using WEX with Node JS, you can make use of the api-runner url's and directly query WEX Engine.
This is how a sample GET query url may look like:
var link1 = 'http://' + WEX_IP + ':9080/vivisimo/cgi-bin/velocity?v.function=query-search&v.username='+username+'&v.password='+password+'&v.app=api-rest&v.indent=true&sources=' + WEX_col_name + '&start=0&num=15&v.app=api-rest&query=sortby:sort_severity%20AND%20sortby:Create_Date_desc%20AND%20Create_Date:>=03/30/2018%20AND%20case_flag:1%20AND%20NOT%20case_flag:0'
Hope this helps.
PS: The WEX API's return data in xml format, so if one is comfortable in xml parsing, one can use that or as in my case, I used xml2json package on node to covert xml to json object and then parse that to display the required fields on the UI.
I am an intern and currently doing automation on a software. What I need to do is to automate the process of creating, and starting an application in the cloud foundry using Rest API (rest-assured). I can't start an app because to start it I need to upload bits. I searched for weeks and still cannot find how to do it. I can only use V2 of the Cloud Foundry API, because when I create an app using the V3 API it doesn't show in the dashboard. I don't know why so we decided to just leave it and use V2 instead.
My question is: Is there any way to create, and deploy/start an app using only Rest API with the V2 API of the Cloud Foundry API? If there is a way to do this by using V3 API, I'm willing to search for the solution to solve the issue.
Thank you very much.
I think others commented on your question to use the cf command line, but if you want to use whats behind the scenes of cf then you can refer to the REST API Docs. At the top the page there is a API version selector (I linked 2.9.0 since you mentioned V2).
More specifically, to create an app you can use the Create App Endpoint; then to upload the bits, you can use Upload Bits Endpoint.
I hope this helps. Definitely check out the main docs, there are tons of endpoints that might be useful. Good luck on your internship!
EDIT: Just in case you need the CF API URL its https://api.ng.bluemix.net
If you want to see how the cli uses the rest api behind the scenes you can temporarily set the environment variable BLUEMIX_TRACE with the command line EXPORT BLUEMIX_TRACE=TRUE.
Then you can try doing cf push or cf start, cf stop, etc, and you will see the http requests the CLI uses. This has helped me a lot versus digging through the CF documentation :). Hope it helps!
I solved it by combining V3 API with V2 API. I understand the upload bits in V3 API. I use link[1] mainly to start the app. I think you can't create a route in V3 API because I don't see any endpoint for that, so I use V2 API instead to create and assign. I also use V2 API to create my app because of what I stated in my question. Thanks for answering the question because without the answers given by good people here I can find the best way to solve this.
[1] Create an App using V3 : https://github.com/cloudfoundry/cloud_controller_ng/wiki/How-to-Create-an-App-Using-V3-of-the-CC-API
[2] V2 API doc : https://apidocs.cloudfoundry.org/3.1.0/routes/list_all_apps_for_the_route.html .
[3] V3 API doc : http://v3-apidocs.cloudfoundry.org/version/release-candidate/index.html#get-assigned-isolation-segment
There is a lot of different Google API dlls for .NET, for example Google.Apis.Calendar.v3. But nothing for Contacts API.
Using older versions or other approaches is not a solution because I already use v3 of several APIs. I need to add a Contacts API.
The Contacts API v3 is supported by the the .NET library for the Google Data API:
https://code.google.com/p/google-gdata/source/browse/#svn%2Ftrunk%2Fclients%2Fcs%2Fsrc%2Fgcontacts
To learn more about its usage, please check the documentation:
https://developers.google.com/google-apps/contacts/v3/