Uploaded image for project: 'Ranger'
  1. Ranger
  2. RANGER-2928

[Ranger Zone REST API] Resources data is missing in XML format

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.1.0
    • 3.0.0, 2.4.0
    • Ranger

    Description

      Observed that the following Ranger Zone API is missing resources in response section for XML format.

      https://<RANGER_HOST>:6182/service/public/v2/api/zones/

      <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
      <rangerSecurityZones>
          <rangerSecurityZone>
              <id>2</id>
              <isEnabled>true</isEnabled>
              <createdBy>Admin</createdBy>
              <updatedBy>Admin</updatedBy>
              <createTime>2020-07-28T10:15:44Z</createTime>
              <updateTime>2020-07-28T10:17:52Z</updateTime>
              <name>test_zone_1</name>
              <services>
                  <entry>
                      <key>cm_ozone</key>
                      <value>
                          <resources/>
                      </value>
                  </entry>
                  <entry>
                      <key>cm_hdfs</key>
                      <value>
                          <resources/>
                      </value>
                  </entry>
              </services>
              <adminUsers>admin</adminUsers>
              <auditUserGroups>public</auditUserGroups>
              <description></description>
          </rangerSecurityZone>
      </rangerSecurityZones>

       

      While the same is present for JSON response.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ramackri Ramachandran
            Shukla Abhishek Shukla
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment