Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-5674

Default behaviour of the Apicast custom logging policy does not correspond to the UI

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • 2.8 GA, 2.9 CR1
    • Gateway
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Hide

      Add the logging policy to the policy chain.
      Update the chain and promote the configuration.
      Send a request.
      Check that the apicast access logs contain the log about the request, even though the logging should be disabled.

      Show
      Add the logging policy to the policy chain. Update the chain and promote the configuration. Send a request. Check that the apicast access logs contain the log about the request, even though the logging should be disabled.

    Description

      When I add the logging policy, the default configuration is empty. With this configuration, the policy behaves as if the enable_access_logs was set to true. When the box is ticked and unticked, the UI looks the same; however, the policy configuration is added with the enable_access_logs set to false and the behavior is further correct. 

      Attached the policy configuration before and after ticking and unticking the checkbox.

      Attachments

        Activity

          People

            Unassigned Unassigned
            drajnoha@redhat.com David Rajnoha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: