| Summary: | [RFE] Azure cloud discovery should allow bulk importing of all subscriptions | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Colin Arnott <carnott> |
| Component: | Providers | Assignee: | John Hardy <jhardy> |
| Status: | CLOSED WONTFIX | QA Contact: | Dave Johnson <dajohnso> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.6.0 | CC: | benglish, bsorota, dajohnso, dberger, gblomqui, hhudgeon, jfrey, jhardy, jocarter, obarenbo |
| Target Milestone: | GA | Keywords: | FutureFeature |
| Target Release: | 5.8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | provider:azure:discover | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1367039 | Environment: | |
| Last Closed: | 2018-02-22 16:40:04 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | Azure | Target Upstream Version: | |
| Bug Depends On: | 1367039 | ||
| Bug Blocks: | |||
|
Comment 2
Colin Arnott
2016-09-15 19:54:05 UTC
Do we want to keep this just a backend change, so that we do the following:
if the subscription field is nil
iterate over all the subscriptions
end
Or does it seem problematic to overload that textbox, and we really need to add a 'all subscriptions' checkbox?
We could do it either way I suppose, perhaps with a note on the form that says, "Leave subscription field blank to discover all subscriptions". But, I think a warning would be good there, too. I'm also wondering, in the case where a user has a lot of subscriptions, if we should default to breaking down each subscription into its own Zone to keep the app from getting hammered too badly. Assigning to myself for QE. You can currently add as many subs per region as you have, but it is manual. But it can be done. There's definitely some ideas floating around Product Management for this. I'm changing the targeted release information on this RFE to 5.8. Assigning to PM for prioritization for 5.8 |