[
https://issues.apache.org/jira/browse/AMBARI-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart Pollock updated AMBARI-8302:
-----------------------------------
Attachment: Select Stack_v1_ambari.png
We have added the standard EULA for Pivotal's products in a HandleBars (*.hbs)
file, which contains a marked-up EULA. The functionality checks for the
existence of a configuration JSON which contains both the path to the EULA and
the version of the EULA. If the version of the EULA is the same as what has
been accepted for a particular version of a stack (e.g. 'BIGTOP-1.0' might have
a few incremental versions of a EULA and the user has accepted version '2' of
the EULA) then the user is not prompted, and the existing functionality
operates. However, if a EULA has yet to be accepted, or the current version of
the EULA is newer than the one which was previously accepted, then the user is
prompted before proceeding.
> Display EULA for specific stacks when available during cluster deployment
> -------------------------------------------------------------------------
>
> Key: AMBARI-8302
> URL: https://issues.apache.org/jira/browse/AMBARI-8302
> Project: Ambari
> Issue Type: Improvement
> Reporter: Newton Alex
> Assignee: Stuart Pollock
> Fix For: 2.0.0
>
> Attachments: Select Stack_v1_ambari.png
>
>
> Some of the Ambari distributions requires users to accept EULA for their
> specific stacks (not Ambari itself but the stacks). For example, if user
> chooses the Bigtop's version of the stack, then they will have to accept
> Bigtop's EULA before proceeding to deployment.
> Ambari should popup the EULA for specific stacks (when available) and prompt
> for yes/no before proceeding. If the user says 'no' then it doesn't go
> forward with the deployment.
> If there are no EULA specified, the behavior should be exactly the same as
> today.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
