Azure API App - Versioning

I have created an API App and I wanted to test the versioning ability. I clicked on the update button on the top ribbon and it asked for confirmation to update. When I clicked yes, nothing has happened. I tried couple of times but no fruitful result. Could
you please assist me in learning/testing this versioning feature that has been introduced with the API App services.

Thanks for reporting this. We do see issue about the update button. We'll remove it soon. The update feature only works with packaged API Apps from the Marketplace. So if you are developing your own API app, it doesn't really apply. For your own API app,
you can use all the deployment options include continuous deployment provided by web app, which is a great way to update your code.
Very soon, we are going to enable you as a 3rd party developer publishing to Marketplace. Then update will apply to your packaged API app as well.

Similar Messages

  • Multiple GET will cause "Add Azure API App Client" to fail

    Hi,
    I'm just playing around with the new Azure App Service API Apps. I've followed the documentation and created the contact list API. I've added to that and created a second GET method with an integer parameter. This works well on the local machine and when
    deployed to Azure. However, when I try to add an App Client I get an enormous error. The important bit, I think, is the message 'Invalid swagger: the operation \"Contacts_Get\" is defined multiple times.' If I remove the second GET message and republish
    then adding an App Client works again.
    Is this a bug or is it a limitation of Swagger. The Swagger UI seems to cope with it effectively.
    Cheers,
    W

    It has to do with how Swashbuckle is auto-generating the operation ids that appear in swagger. The Logic App designer only wants to have 1 operation for each operation id -- it doesn't like ambiguity.
    I built out a library to help cope with this and other issues
    over here, if you use that you can provide a unique "friendly name" for each action (which will then generate a title cased operation id for each).
    In the alternative, you could write a custom operation filter to feed to Swashbuckle to override the operation ids that it is generating for you in the background. You can see how to do that
    over here.

  • Azure App Service API app triggers feedback

    Hi
    I am kinda new to this and when I tried to build a trigger as defined in the article
    http://azure.microsoft.com/en-us/documentation/articles/app-service-api-dotnet-triggers/ I simply do not seem to know what I am doing wrong.
    I get a lot of compilation errors just using the code in a ASP Net Web Applicaton project, using the Azure API App template. I tried to place the code in a controller but then I get complation errors on a couple of places. The most noticable:
    return
    this.Request.EventTriggered(new{
    files = touchedFiles });
    The EventTrigger extension method does not seem to exist. What am I doing wrong?
    //Mikael Sand - <a href="http://mikaelsand.se"> Blog</a> Enfo Zystems Sweden

    Hey Mikael!
    I actually was struggling through pretty much the same things at the same time that you were.
    The EventTriggered extension is actually in the Microsoft.Azure.AppService.ApiApps.Service namespace, so without a using directive for that it will not be happy.
    I created a library to help with the metadata generation required for Triggers, and did a write-up on exactly what it takes to create both a polling and push trigger (with a few more samples) here: https://github.com/nihaue/TRex#building-a-polling-trigger-api-app
    Hopefully having that combined with
    the official docs, and also
    Sameer's sample can get you on the right track.
    Hope that helps!

  • Welcome to the Azure App Service API Apps Preview Forum!

    Welcome to the forum! This forum is for support of our customers who are using API Apps. Feel free to post any questions you have related to API Apps.
    The Azure App Service API Apps Team
    Jim Cheshire | Microsoft

    Hey Mikael!
    I actually was struggling through pretty much the same things at the same time that you were.
    The EventTriggered extension is actually in the Microsoft.Azure.AppService.ApiApps.Service namespace, so without a using directive for that it will not be happy.
    I created a library to help with the metadata generation required for Triggers, and did a write-up on exactly what it takes to create both a polling and push trigger (with a few more samples) here: https://github.com/nihaue/TRex#building-a-polling-trigger-api-app
    Hopefully having that combined with
    the official docs, and also
    Sameer's sample can get you on the right track.
    Hope that helps!

  • Getting app version string via the API, in AE 6.5 and 7.0

    Hi-
    I was wondering if there's a way to get the application version string
    (such as "7.0x244") by using API functions.
    This is doable with scripting, by calling app.version(), but I couldn't find an equivalent function in the API/SDK.

    There's no way to get the version as a string, though both the effect API and AEGP API provide versioning info.

  • Logic App does not get Swagger Data from API App

    I'm following the tutorial here: http://azure.microsoft.com/en-us/documentation/articles/app-service-dotnet-deploy-api-app/
    I successfully added the API app, but when I add it to a Logic App, it gives the error: "Error fetching swagger api definition. Please try again."
    What is going on? I know the swagger is working properly, because I'm able to consume it from the API app.
    Thanks,

    I have the same issue. Those links don't help and you really have not answered the question.
    I'm using the basic WebApi service that is created by visual studio (plain vanilla string inputs/outputs for all the Http Verbs). The swagger works correctly, but when I deploy to my logic app I get:
    If I browse to the Api App itself I can see the swagger definitions working correctly but there is indeed a red validation warning. If I click the link, however, the validator returns Http 500 Internal Server Error.
    There is some talk on stackoverflow that this is to do with the https certificate that MS is using, and sure enough, if I download the swagger output from the Api App and upload it to a plain http url on another site, it validates correctly.
    So: this seems insoluble. The swagger is correct, but is failing validation, and the Api App cannot be consumed by the logic app.
    Here is the Api App endpoint showing the error: https://microsoft-apiapp4b8b7674e41e4a8f905a2d8b1e4a745b.azurewebsites.net/swagger/ui/index
    And here is the swagger from https://microsoft-apiapp4b8b7674e41e4a8f905a2d8b1e4a745b.azurewebsites.net:443/swagger/docs/v1 
    {"swagger":"2.0","info":{"version":"v1","title":"PE-Services-Idml"},"host":"microsoft-apiapp4b8b7674e41e4a8f905a2d8b1e4a745b.azurewebsites.net:443","schemes":["https"],"paths":{"/api/ToEpl":{"get":{"tags":["ToEpl"],"operationId":"ToEpl_Get","consumes":[],"produces":["application/json","text/json","application/xml","text/xml"],"responses":{"200":{"description":"OK","schema":{"type":"array","items":{"type":"string"}}}},"deprecated":false},"post":{"tags":["ToEpl"],"operationId":"ToEpl_Post","consumes":["application/json","text/json","application/xml","text/xml","application/x-www-form-urlencoded"],"produces":[],"parameters":[{"name":"value","in":"body","required":true,"schema":{"type":"string"}}],"responses":{"204":{"description":"No
    Content"}},"deprecated":false}},"/api/ToEpl/{id}":{"get":{"tags":["ToEpl"],"operationId":"ToEpl_Get","consumes":[],"produces":["application/json","text/json","application/xml","text/xml"],"parameters":[{"name":"id","in":"path","required":true,"type":"integer","format":"int32"}],"responses":{"200":{"description":"OK","schema":{"type":"string"}}},"deprecated":false},"put":{"tags":["ToEpl"],"operationId":"ToEpl_Put","consumes":["application/json","text/json","application/xml","text/xml","application/x-www-form-urlencoded"],"produces":[],"parameters":[{"name":"id","in":"path","required":true,"type":"integer","format":"int32"},{"name":"value","in":"body","required":true,"schema":{"type":"string"}}],"responses":{"204":{"description":"No
    Content"}},"deprecated":false},"delete":{"tags":["ToEpl"],"operationId":"ToEpl_Delete","consumes":[],"produces":[],"parameters":[{"name":"id","in":"path","required":true,"type":"integer","format":"int32"}],"responses":{"204":{"description":"No
    Content"}},"deprecated":false}}},"definitions":{}}

  • Deployment to Azure Web App from TFS not updating

    Hi all,
    I'm having a problem with deployments to my azure web app. I'm committing my code to Visual Studio Online and then running a build to get VSO to deploy the code to Azure. The deployment seems to work fine (there are no errors that I can see)
    but often the files aren't updating on the website. I'm getting errors for old code and when I view the pages in question online (using the VSO editor), they look fine. Has anyone come across this issue before?

    Hi David,
    The errors I've been getting belong to old versions of files not being refreshed. For example, I changed one of my mvc views to take a different model. After deploying the code, the controller was sending in the new model but because the view didn't update,
    it was expecting the old model to be passed in and hence caused a runtime error. It seems to me like Azure is caching certain files. I think that is the case because when I viewed that view file I changed in the VSO editor, it showed the correct code but the
    front end was still showing the old code.
    The only thing I've been able to do that has worked reliably over the last week is stopping the website, deploying the code and then starting the website. The code gets deployed correctly every time I do that. This is not an ideal scenario and I'm hoping
    there's something that can be done.

  • Azure Web Apps (Web Sites) vs Azure Cloud Services (Web Roles)

    Hi All,
    Need some help in choosing between the Web App or a Web Role for a MVC5 application that we are going to build. We are planning to build an MVC5 application which will consume a Web API (hosted on Azure). The MVC5 application would be an external site and
    it needs to be load balanced and it would be hosted on Azure.
    We are not able to decide on the hosting options for the same ... between Azure Web Apps and a Web Role. We didnt come across anything which will help us to make a choice as to where the Web Apps fall short or which one should one go for etc.
    Any help on this front would be highly appreciated.
    Regards,
    Saurabh

    To make your life easier you should start by using Web Apps, they have many more features than Web Roles (git deployment, backup, free sku, webjobs, continuous integration and many more).
    There are some scenarios that are not supported like remote desktop to the VM.
    But the reason you should start with them is that unlike Web Roles you won't have any special code relying on the environment you are running on so you will be able to easily move to web roles in case you find a scenario that is not supported by Web Apps.

  • Azure API and tokens issued by azure AD

    anyone know of a sample that showcases the azure API management/delivery feature consuming (access) tokens issued by Azure AD?
    is there a reasons why its not even a sensible thing to conceive? (it seems obvious...but perhaps I have a disconnect somewhere)

    perhaps a useful comment flows from this:
    The documentation (at github, on AAD samples) is very engineering centric. Its very correct; very precise, overly so. It embeds best practices within (without teaching how to think about which of the 10 flows are proper, for different scenarios); and sometimes
    calls things opened connect, sometimes oauth2. Distinguishing the differences is the subtle art of interpreting Microsoft engineering speak.
    I learned 10 years not to program Microsoft apps in a way that is not demonstrated by an official sample. Thus the lack of a AAD sample of Azure API is problematic. I don't know (having been burned 100 times) that the OAUTH2 mentioned in the API docs is
    compatible with one of the oauth2 flows of AAD sample land.
    call me over thinker, if you like. But, this is what its like to be on the en d of the fragmented, drip drip, ALL change EVERY  3 years, communications style in windows/azure/win32 comsec.
    i suspect the fix is another attempt at a best practices document - with best practice teaching samples - similar to those that so excellently rounded out WIF work, in the last generation of efforts.

  • Azure Web Apps extremely unstable following switch from VMs

    Last week we made the switch from Azure VMs to Azure Web Apps (web sites). The main reason for doing so was to take advantage of continuous deployment, auto-scaling and deployment slots.
    We have 4 web apps running on S2 instances (currently scaling up to 2 instances). We then have 4 other virtual machines that host our databases (RavenDB) and another web app that cannot be hosted on Web Apps. We're using VNETs to connect everything together.
    Previously the entire system was hosted on just 2 virtual machines.
    A week on we're finding
    a) Performance has degraded
    b) The Web Apps (and associated service) are increasingly unreliable
    We used to deploy frequently throughout the day without issue. Since moving to Web Apps we regularly experience 503 errors for up to a minute following a deployment. We switched to staging slots to try and circumvent this but even this hasn't been foolproof.
    We're now actually reluctant to deploy changes to our API during the day because it has been so unreliable.
    Performance has also suffered - we're using New Relic for monitoring and our throughput has halved since moving to Web Apps despite the web apps actually having more resources than they did before.
    Auto-scaling has also been very hit and miss. Our apps rarely put any load on CPU but they can use quite a lot of memory. We set up auto-scaling based on memory but rather unhelpfully the new portal changed our "less than or equal to" scaling rule
    to "equal to" meaning that the instances never scaled down - thanks Azure! I believe this is still an issue in the portal.
    We've gone from almost 6 months of 100% uptime to a week of regular issues. We deployed a new web app today and attached it to the same to virtual network used by our other apps and it caused a disruption in the other apps - our API could no longer contact
    the virtual machine hosting RavenDB.
    All-in-all this has not been a great experience and if it's a choice between reliability/performance and the bells and whistles that Azure Web Apps provide, I'll be going back to VMs.

    Hi David,
    It's an ASP.NET Web API application and we're deploying with Web Deploy.
    When we first switched to Web Apps and deployed directly to the "live" instance we found that we were getting 503 errors. There were no errors in our application logs (Elmah) so I'm assuming this is an issue outside of the application. We do have
    250 or so sites that are serviced by the API so I would expect a slight delay whilst the application starts but certainly not a 503. In some cases we had to re-deploy (the same code) to get things back.
    We then switched to using Staging Slots to try and avoid this issue. Whilst this avoided the 503 errors most of the time, the time it takes for the application to come back up following a deployment has increased dramatically - and this is despite "hot
    swapping" from staging to production.
    Yesterday I tested this by deploying to staging and then swapping the deployment. It took over 30 seconds following the swap before the API was available. When I used to deploy to the VM it was available almost immediately.

  • Azure API Management - external endpoints

    Hi,
    I'm trying to implement the following scenario by using the preview Azure API management.
    I have a Web API, hosted in an OnPrem IIS. I want to expose this API via the Azure API Management.
    How can I manage exposing an OnPrem endpoint? Must I first be sure that my existing OnPrem API is published on the Internet? Or can I use a Service Bus Relay endpoint?
    Thanks.

    Hi David,
    Thanks for posting!
    Base on my understanding, If your website is hosted on-permission( Intranet), you need expose the endpoints for Azure API management , and you need use the http or https endpoints for this feature. You could use azure service bus service to expose
    your endpoints like this blog (http://blogs.msdn.com/b/paolos/archive/2013/10/24/how-to-integrate-a-windows-azure-web-site-with-a-lob-app-via-a-service-bus-relay-service.aspx
    ) and this thread  (http://stackoverflow.com/questions/9626386/relay-webhttprelaybinding-to-webapi-service ), Also, you could publish the site on internet
    and use the API url (http://blogs.iis.net/tomkmvp/archive/2010/02/03/how-do-you-access-iis-behind-a-nat-router.aspx ).If I am misunderstanding , please
    let me know free.
    Regards,
    Will
    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click
    HERE to participate the survey.

  • Azure API Manager ALM

    Would like some good documentation on best practices for ALM with Azure API Manager. 
    For example...
    How do people have their DEV/TEST/PROD environment setup and how do you deploy changes?
    We are thinking about using the dev teir for our development and test environmnet and then the standard version for production. Are we on the right path?

    Hi Dan, you are definitely on the right path.
    Besides, below features might be useful to help you manage your environments:
    1. Management Rest API: this is useful if you want to manage your environment programmatically.
    http://msdn.microsoft.com/en-us/library/azure/dn776326.aspx
    2. Backup/Restore: http://azure.microsoft.com/en-us/documentation/articles/api-management-howto-disaster-recovery-backup-restore/
    Please let us know if you have any questions.
    Regards,
    Miao

  • Adding API App Host to Virtual Network fails

    I've been trying for 2 days now to add an existing API App Host to a Virtual Network, but it errors with notification "VPNNetworkSetupFailure" and then the blade continues to say "Something went wrong" in the Networking tile.  The
    API App is DTSharedDimensions in subscription 8bc2fde5-e1ad-4bc0-9287-85957096f0b4.
     Any help will be appreciated.
    On another note - the API App blade doesn't list any API Apps, I have to go to the App Service Plan blade and navigate from there to the API App and the API App Host.

    API Apps are hosted on Web apps. From Azure portal, you can use the following steps to navigate to the hosting Web App and enable Virtual Network.
    API App blade -> Essential part on the top of the blade -> API App Host link

  • Use node.js for API Apps

    From the description for API Apps, it appears as though node.js is supported, but there is no documentation on how to use node.js.  The existing documentation shows how to use Visual Studio and c#.  I understand this is a preview, but was wondering
    if I can bring over a node.js app that has been built using the hapi framework.  If not yet, will node support be expected prior to GA?
    Thanks,
    Alex

    Thanks for the question, Alex.
    You can definitely implement an API app in Node.js. We'll add articles and samples soon. Following is what you can do.
    Create an empty API app from Azure portal. It's in the +New button. In Azure Portal, you can navigate to the API app blade, then navigate to the host of it from the essential UI to its hosting web app.
    Use your favorite Node.js framework to implement your REST API. Add an apiapp.json file to the root folder of your project. Configure it as show in "Review apiapp.json" section of
    http://azure.microsoft.com/en-us/documentation/articles/app-service-dotnet-create-api-app-visual-studio/.
    For getting Swagger 2.0 in Node.js, you may want to check out
    https://github.com/krakenjs/swaggerize-express.
    Use your favorite deployment option to deploy your Node.js app to the hosting web app.
    Restart the gateway in Azure portal to have it refresh the registration of the API app

  • Continuous deployment in API App

    The new API App hosting does not provide a feature to add continuous deployment with Visual studio online. It has option only to select any existing project. The old azure portal does not reflect the API App that I have created under Web App. I expect
    to see that API App available under Web App so that I should be able to configure the continuous deployment with visual studio online. Or I need an option in API App to add a new team project for continuous deployment. Alternatively I can create a dummy Web
    Apps and setup continuous deployment and reuse the team project in my API App that I have just created. 

    If you have the publish settings file for an existing API App you should be able to deploy it using MSBuild. The actual publish-time experience is almost identical to the traditional Website publish experience; it's all MSBuild and Web Deploy. Have you
    tried this out yet? 

Maybe you are looking for