[jira] [Commented] (CLOUDSTACK-6068) service/disk_offering_details: display flag should be set to true by default

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896827#comment-13896827 ] 

ASF subversion and git services commented on CLOUDSTACK-6068:
-------------------------------------------------------------

Commit aff22869cc18bcfb0845af2624fdd2afeabb3787 in branch refs/heads/4.3-forward from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aff2286 ]

CLOUDSTACK-6068: set display flag to true in service/disk_offering_details tables


> service/disk_offering_details: display flag should be set to true by default
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6068
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6068
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>            Reporter: Alena Prokharchyk
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> There are 2 tables where details for service/disk offering details are stored:
> service_offering_details and disk_offering_details.
> Each table has "display" field (boolean) - if set to false, the detail will be displayed to admin only. 
> Bug: initially the default value of the db field was set to false, so all the details were saved with 0 flag (although admin didn't intend it). But the API was working w/o checking this field before, so details with 0 were returned to the user. Then this API bug was fixed, and the details stopped returning to the user.
> Fix: we have to set the display flag to be 1 by default. Only when its defined otherwise in the API, this flag should be set to 0



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)