Bug 1501454 - Backport cloud_subnet API collections to CloudForms
Summary: Backport cloud_subnet API collections to CloudForms
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: API
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.9.0
Assignee: Tim Wade
QA Contact: Martin Kourim
URL:
Whiteboard:
Depends On:
Blocks: 1524646
TreeView+ depends on / blocked
 
Reported: 2017-10-12 15:21 UTC by Robb Manes
Modified: 2021-06-10 13:15 UTC (History)
7 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1524646 (view as bug list)
Environment:
Last Closed: 2018-03-06 14:32:58 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Robb Manes 2017-10-12 15:21:27 UTC
Description of problem:
A commit exists to allow cloud subnets to be controlled via an API collection, available here:

https://github.com/ManageIQ/manageiq/commit/d63393e98cfbc0ed4e58ac1ad14836d10b2f5579

It is already merged into current MIQ master branch:

$ curl -u admin:smartvm localhost:3000/api/cloud_subnets | python -mjson.tool
{
    "actions": [
	{
	    "href": "http://localhost:3000/api/cloud_subnets",
	    "method": "post",
	    "name": "query"
	}
    ],
    "count": 3,
    "name": "cloud_subnets",
    "resources": [
	{
	    "href": "http://localhost:3000/api/cloud_subnets/3"
	},
	{
	    "href": "http://localhost:3000/api/cloud_subnets/2"
	},
	{
	    "href": "http://localhost:3000/api/cloud_subnets/1"
	}
    ],
    "subcount": 3
}

A customer is requesting this be pulled into the next release of CloudForms.

Version-Release number of selected component (if applicable):
Desiring pull into next release, 4.6 if at all possible (or ETA if it is not).

How reproducible:
N/A

Steps to Reproduce:
N/A

Comment 6 Martin Kourim 2018-02-15 15:34:20 UTC
Verified that the cloud_subnets collection is present in the 5.9.0.20


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