API and Asset Versions
Introduction
With the latest version of Anypoint Platform (Version 2), some new concepts have been introduced regarding the versioning of APIs. Here in this article, I will try to make use of them. The official documentation of Mulesoft does not talk too much about this aspect. Through this article, I would like to create an open discussion about the versioning of APIs.
Versioning of API
The versioning of an API is a complex topic. In this post, I will provide a simple use case scenario that discusses the features provided by Anypoint Platform (Titan). https://goo.gl/wRTrzZ #DataIntegration #ML
How and Why to Use an OAuth Proxy URL With Cloud Elements
#ICYMI: Ok, so that title should really read “Why and How…” since I plan on starting with the “Why” then moving to the “how”, but I don’t look backwards and neither should you. You’re an engineer and you have code to write, and I have a blog to write. So, off we go!
The Why
Some API providers only allow you to use a single callback URL when using an OAuth flow. Why? I haven’t the foggiest of ideas. That’s the route they decided to go, so Cloud Elements implemented a way for you to use a single callback to service multiple environments. Let’s say you have a single app for a Box integration your building. With that single app, you want to be able to hit both your testing and production environments. Well, out of the box (See what I did there) the provider does not allow that. So you can either spin up two apps, have environment variables in your code, and make a lot more work for yourself (Who has the time?). OR you can have one app with a proxy URL as the OAuth callback which has the ability to hit either environment. Your call, I’ll wait while you decide… https://goo.gl/kFu2wZ #DataIntegration #ML