[ 
https://issues.apache.org/jira/browse/NIFI-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zackeus Bengtsson updated NIFI-12302:
-------------------------------------
    Description: 
In the generated swagger.json api definition, objects that contain the 
BundleType enum, like BundleInfo, have the wrong enum values. The enum values 
for bundleType should be "nifi-nar" and "minifi-cpp", but are currently 
"NIFI_NAR" and "MINIFI_CPP". For the endpoint resource defenitions in the 
swagger file, the enum values are correctly generated.

For the BundleType object, the values are correct. The issue only occurs for 
objects using the containing the enum object

  was:In the generated swagger.json api definition, objects that contain the 
BundleType enum, like BundleInfo, have the wrong enum values. The enum values 
for bundleType should be "nifi-nar" and "minifi-cpp", but are currently 
"NIFI_NAR" and "MINIFI_CPP". For the endpoint resource defenitions in the 
swagger file, the enum values are correctly generated.


> Registry swagger enums are generated with incorrect values
> ----------------------------------------------------------
>
>                 Key: NIFI-12302
>                 URL: https://issues.apache.org/jira/browse/NIFI-12302
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: NiFi Registry
>    Affects Versions: 2.0.0, 1.24.0, 1.23.2
>            Reporter: Zackeus Bengtsson
>            Priority: Minor
>
> In the generated swagger.json api definition, objects that contain the 
> BundleType enum, like BundleInfo, have the wrong enum values. The enum values 
> for bundleType should be "nifi-nar" and "minifi-cpp", but are currently 
> "NIFI_NAR" and "MINIFI_CPP". For the endpoint resource defenitions in the 
> swagger file, the enum values are correctly generated.
> For the BundleType object, the values are correct. The issue only occurs for 
> objects using the containing the enum object



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to