t: Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure
- second thoughts
A feedback mechanism for users is obviously a "good thing", but IMO, not
germane to the threads original purpose of how and when to expose supported
resources in Heat. I cannot imagine us im
tor easily know the users
> actually need something they aren't providing gives them the opportunity to
> fix the issue, benefiting all 3 parties.
>
> Thanks,
> Kevin
>
>
> From: Randall Burt [randall.b...@rackspace.com]
> Sent: Tue
Randall Burt [randall.b...@rackspace.com]
Sent: Tuesday, July 14, 2015 2:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Heat] [app-catalog] conditional resource exposure
- secondthoughts
Making users complain to admins that may have litt
Making users complain to admins that may have little to no control over what is
and isn't available isn't a healthy strategy for user experience. Purposefully
engineering hardship to try and influence operators to "do the right thing" in
someone else's opinion sounds pretty counter productive to
We're kind of debating the same thing for the app catalog. Do we show templates
that don't work on a given cloud since they wont work, potentially making
useful tools hard to discover, or do we view it as an opportunity for users to
complain to their admins that they need X feature in order to d
