I am using the YangUI on the REST API of ODL(Oxygen Release) and I want to use the config features of opendaylight-inventory but I can only see the operational ones. Like this.
¿What can be the problem?
I have solved installing the same features on a previous ODL release. I don't know why but I can't see config features on Oxygen.
Related
I am trying to implement an API gateway which has java plugin support. Have analyzed Kong, APIMan, APIsix, of which APIsix seems to be the best fit. But when i am trying to see the java plugin support, the github for java plugin runner displays as "This project is currently considered experimental."
https://github.com/apache/apisix-java-plugin-runner
So wanted to check with community, if that plugin is experimental and is there any other way to use ApiSix for production with java plugins enabled.
Anymore options for java enabled plugin API gateways are also welcomed.
So I'll quote out the reply that I had received for the same question on the slack channel from one of the maintainers of the project, for reference.
In fact, from some information I’ve gathered, there are already some users using it in production environments.
I can’t give an answer about whether it should be marked as production-ready or not. Here are some facts.
the design pattern, API interface and custom development approach of this project has not changed significantly since its inception, and should not be a major upheaval in the future, as it follows some common gateway design approaches in the Java world.
it is currently used in a rather primitive way, requiring clone project source code, but in the Java world, mature projects should import dependencies and use them by defining GAV in the dependency file.
Based on this, I think it is now production-ready in terms of stability, but not enough on other levels.
Apache APISIX Slack channel has the same question, link: https://the-asf.slack.com/archives/CUC5MN17A/p1653908139962639
Back to this question: Java Plugin Runner is used in production by some community users.
Here's the thing, from what I know, It has been used in a production environment in China(You can refer to this from the community bio-weekly talk).
So I would suggest you can try it.
Also, the plugin is still relatively easy to suit and I think could be better customized to suit your needs.
I'am currently trying to understand the discovering of JAXRS-Endpoints in Quarkus. My assumption is that they are automatically discovered and there is no need to register them. In addition I tried to import Endpoints from an other module/jar File. It is working to out of the box.
But than I tried to understand the order of discovering endpoints.
I tried to overwrite a jar file provided endpoint in my application, but it is not working. Therfore in my opinion there is a potential security problem, if any third party module can overwrite my endpoints. Has anyone the same problems and can provide me informations how to think about this problem? (My only solution is to write an own extension which removes all endpoints an add only the ones I want to have, but I think this is against the idea)
Thanks in advance!
Duplicate endpoint detection was added to RESTEasy Reactive in https://github.com/quarkusio/quarkus/pull/15037.
This means that from version 2.7.0.CR1 and on, Quarkus will fail the build if duplicate JAX-RS endpoints are defined (assuming you are using quarkus-resteasy-reactive).
I'm working on a API project on a hybrid cloud. APIs are hosted on-premise and via the cloud service (Azure API Management service), the APIs are exposed to the external world. For any APIs, we are writing the contract in Open API Specification as Yaml file manually and then import it into Azure APIM. Everytime yaml is imported in APIM, the version number in the Yaml get's reset to 1.0, even though it is something different in the Yaml file (unless we modify it manually after the import). This is creating confusion on what version is in the cloud vs what version is there locally. So, I'm looking for option if anybody faced this issue and how did they resolve it? One of the workaround solution that we have been doing is writing the version number in description when revising the version in Azure APIM.
You could create a new version of an existing API and then import your updated OpenAPI spec using the update method as below
Also, something that you might already be doing is to maintain your OpenAPI specs in a git repository for version control since its like any file.
I found few typos/mistakes in Spring Boot reference guide.
Could you please suggest whom can I contact, or even better how to fix it myself (e.g via pull request if possible) ?
I checked spring GitHub repository but spring-boot-actuator-docs seems to have nothing to do with reference guide.
Thanks in advance.
Spring Boot is like any regular github project. It is located here:
https://github.com/spring-projects/spring-boot
If you want to fix the typos, create a pull request. You'll find all you need to know in our contributing page. The documentation is located in the spring-boot-docs module
Does anyone know what the state is of the Spring Integration Extensions at https://github.com/spring-projects/spring-integration-extensions ?
Some seem outdated with regards to Spring versions. And others, whilst updated, don't seem to have recent releases or snapshots available at http://repo.spring.io/libs-snapshot/org/springframework/integration/ .
For example I wanted to integrate with AWS, but cant find a release or snapshot for the latest version of Spring Integration. And SQS support has been "coming soon" for some time.
The outdatedness of those that do exist, and lack of clarity on what is intended, make me concerned to use any of them. Does anyone know what the Spring team's intention is with regards to the release cycle of these extensions? Are they viewed as incubators that will eventually move into Spring Integration core, or something else?
Cheers,
Menno
Spring Integration extensions are community provided, and they will constantly change according to the will of the community. Your best chance is to get in touch with the contributors of the AWS extension.
You should use them, once you understand what they are doing, there are no more guarantees than other Spring projects, only the fact that others are also using it.