We are trying to implement CORS support in our APIs, and it we are getting an error from API Manager that is exactly the same as what is described here.
We are using API Manager 1.3.
Can someone confirm that there is no way to support OPTIONS with API Manager 1.3? We don't want to upgrade to 1.4 at this time.
There was another issue which we found when using PUT and OPTIONS method from APIs as described in [1].
This was fixed with AM 1.4.0.Hence better option is to upgrade to 1.4.0 as it contains fix for both your mentioned issue and mine mentioned one.And additionally AM 1.4.0 contains several new features with it.
[1] https://issues.apache.org/jira/browse/SYNAPSE-919
Thanks;
Related
till now i am working with V1 of the SDK, how ever I need to support IMDSV2. although in the V1 code I see it support it, actually it isnt, as I still getting 401 and it seems that I need to query the token and pass it to the metadata utils. I wanted to see if in V2 it was fixed, but i dont see in their doc, how to interact with the metadata service
spring cloud 1.12 resolved the issue for me. This version supports IMDSv2 and not the older ones.
(I know that this sounds as a newbie questions, but, you know, really, I don't finde the answer in docs)
In WSO2 products, and specifically in API Manager (2.1.0), we have to modify a lot of configuration files just to start.
We have seen that some configuration files (api-manager.xml, carbon.xml) use configurations variables. E.g., ${admin.username} to substitute by admin user.
We have found an old post (2016) explaining the use of configuration variables in WSO2 products
https://medium.com/#shan1024/overriding-configurations-in-wso2-products-using-deployment-properties-file-f096e96f782d
But we are not able to find the deployment.properties files referenced in that post, neither and official documentation.
Do you know if this works in APIM? Where have I to install this file?
As far as I know, deployment.yaml was introduced in Carbon kernel 5.2 onwards. But WSO2 APIM 2.x is based on Carbon kernel 4.4.X. Therefore APIM 2.x doesn't support that.
WSO2 APIM 3.X will support this feature.
I'm considering using GraphQL with a Django backend service but I couldn't find much information regarding the API documentation. I need some solution to dynamically generate the documentation, perhaps like npm's graphql-docs with a result similar to GitHub's API docs.
Is it feasible to accomplish with graphene-django? If not, what's a good alternative for a python environment?
Yes, it's very easy to do by using GraphiQL, which is embedded in to Graphene.
The instructions on how to integrate this with Graphene are here in the graphene-python documentation. --- basically you need to add the parameter graphiql=True when setting up the API route in your urls.py file.
After it is set up, if go to your API endpoint in your browser, you'll see a nice interface for sending API calls, getting API responses, and reading documentation for both queries and mutations. The documentation is initially hidden on the right until you click on the "< Docs" link.
API manager import/export tool is useful in a situation where the api is not available at all in the target environment. What is the best way to move the updates to an API from one environment to another, without incrementing the API version?
I can think of a way to remove the API in the target environment, and import the updated API zip file again. Is there a better way to achieve this?
I believe this issue has been fixed in wso2am 2.1 version. Following is JIRA opened for exactly same scenario you have explained above.
APIMANAGER-4569Support updating an API with API import tool
WSO2-API-Manager-2-1-0 release note says so.[APIMANAGER-4569] - Support updating an API with API import tool
I have not try it myself, you may want to try new version. Thanks.
I'm new to Facebook development. I'm working on migrating an existing app in accordance to the Graph API upgrade guide. I'm looking for guidance around calls such as api.facebook.com/method/Fql.multiquery.
My question is: does this type of API need to be upgraded as well, or does it only apply to graph.facebook.com calls? I want to ensure that api.facebook.com/method/Fql.multiquery calls will still work after 4/30/15.
You may want to take a look at the Batch Requests of the Graph API. You can also specify dependencies between the requests.
Calls to http://api.facebook.com/method/Fql.multiquery will no longer work. The REST API is long deprecated anyway.
As #luschn said, you have to migrate to the Graph APIs batch requests, and use the /fql endpoint. You can only use FQL if you have a v2.0 app, and not higher.