Closed xjjh1 closed 2 years ago
Hi @xjjh1 - This is working as expected. This is because of the API Product payload you are passing. With the introduction of Operation Groups and GraphQL, the payload for creating the API Products are changed too. For backward compatibility, the previous payload still works and hence you see the legacy API Product warning. For the new API Product, you can refer this sample where I have both examples. Try it out and let me know if you have any other issues. If it works, then please update here and close the issue
Hi @ssvaidyanathan
Thanks for the details. I overlooked it.
I have tested it and it works.
Tested in Hybrid 1.6 and 1.7, apigee-config-maven-plugin: 2.4.0
Below warning is shown on the API product when an API product is created using this plugin
This API product is created in legacy format so API resources and API paths shown below, may only be present in this case.
API products are getting created but the UI is showing in old/odd format. The operations section in the API product is different when it is created with this maven plugin compared to the API products created in GUI.
Please refer to the images attached below, you can notice the difference in operations and other sections.
Without Warning - api product created via UI:
With Warning - using this maven plugin:
FYI - @msadasivam @ssvaidyanathan