Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1489#issuecomment-215479369
In reading this, is it the case that if someone upgrades from a previous
version to 4.9 (with this code included) they will not be able to take
advantage of this functionality? Maybe I did not understand those details
correctly. This is just a clarification so I know what to expect (I have
customers who are interested in this functionality).
@koushik-das Regarding: "Regarding writing a plugin, I meant that if
someone really needed a functionality like this, they could have easily
developed it outside of Cloudstack as well (like some kind of portal calling
Cloudstack APIs)." Given that I work a company who has done exactly that, I
can assure you it is not "easy" and takes a huge development effort to recreate
all the functionality provided by the ACS UI. This is not really a viable
option for people looking for this feature.
@koushik-das I also don't understand this "Any blocker (including security
bugs) in this will make the 4.9 release unusable for new installs as this the
only authorisation mechanism for entering into the system.". Can you explain
what you mean? How does this feature and a 'blocker bug' render 4.9 unusable?
I am not quite following this. Maybe someone else can also chime in to help
explain his concerns.
Thx...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
