Bug 1300965 - Search Bookmarks - public attribute not mandatory
Summary: Search Bookmarks - public attribute not mandatory
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-22 08:53 UTC by Roman Plevka
Modified: 2019-02-25 21:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 21:09:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Roman Plevka 2016-01-22 08:53:50 UTC
Description of problem:
While creating a Search Bookmark using API, server does not require a 'public' attribute to be set, resulting new Bookmark entity with 'public': Null
- both foreman and katello entities are affected

Version-Release number of selected component (if applicable):

# rpm -q katello
katello-2.5.0-2.nightly.el7.noarch

# rpm -qa *katello
katello-2.5.0-2.nightly.el7.noarch
tfm-rubygem-hammer_cli_katello-0.0.19-1.el7.noarch
tfm-rubygem-katello-2.5.0-.201512150057git5d138841.nightly.el7.noarch
pulp-katello-0.4-3.el7.noarch



How reproducible:
always

Steps to Reproduce:
1. use POST request to create a bookmark for a random controller:

# curl -ku admin:changeme -H Content-Type:application/json -d "{\"name\": \"foo\", \"query\":\"bar\", \"controller\":\"architectures\"}" 'https://<FQDN>/api/bookmarks'

Actual results:
"public": null

{"name":"foo", "controller":"architectures","query":"bar","public":null,"id":1364,"owner_id":3,"owner_type":"User"}

Expected results:
"errors":{"public":["can't be blank"]}
or a default value true/false

Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:06:22 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Bryan Kearney 2017-01-13 21:09:57 UTC
This is an older bug which I do not envision being addressed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.


Note You need to log in before you can comment on or make changes to this bug.