[doc] Monasca API spec: get alarm count is not formatted correctly

Bug #1696393 reported by Emma Foley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Monasca
Fix Released
Undecided
Emma Foley

Bug Description

The spec for Get Alarm Count appears literally as:

  ##Get Alarm Counts Get the number of alarms that match the criteria.

  ###GET /v2.0/alarms/count

  ####Headers

  X-Auth-Token (string, required) - Keystone auth token
  Content-Type (string, required) - application/json
  Accept (string) - application/json
  ####Path Parameters None

  ####Query Parameters

It should be formatted like the corresponding entries

e.g. https://github.com/openstack/monasca-api/blob/e79e64e71d1d5aa033dac23f60cbdaec661696c7/docs/monasca-api-spec.md#list-alarms

Changed in monasca:
assignee: nobody → Emma Foley (emma-l-foley)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to monasca-api (master)

Fix proposed to branch: master
Review: https://review.openstack.org/471741

Changed in monasca:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to monasca-api (master)

Reviewed: https://review.openstack.org/471741
Committed: https://git.openstack.org/cgit/openstack/monasca-api/commit/?id=73066257a829b6dfa3d4dff9a5702ccb975c418d
Submitter: Jenkins
Branch: master

commit 73066257a829b6dfa3d4dff9a5702ccb975c418d
Author: Emma Foley <email address hidden>
Date: Wed Jun 7 11:03:19 2017 +0000

    [doc] Fix incorrect formatting on get alarm count

    The spec for Get Alarm Count was appearing literally as:

      ##Get Alarm Counts Get the number of alarms that match the criteria.

      ###GET /v2.0/alarms/count
      etc.

    It is now formatted so that the headings are rendered like corresponding entries.

    Change-Id: Ic8ddc1fc3f56c00f22e8c0132a49be2cc7cd2fc1
    Closes-Bug: #1696393

Changed in monasca:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/monasca-api 2.2.0

This issue was fixed in the openstack/monasca-api 2.2.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.