Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 92FAF18620 for ; Fri, 25 Sep 2015 22:14:04 +0000 (UTC) Received: (qmail 22759 invoked by uid 500); 25 Sep 2015 22:14:04 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 22719 invoked by uid 500); 25 Sep 2015 22:14:04 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 22678 invoked by uid 99); 25 Sep 2015 22:14:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2015 22:14:04 +0000 Date: Fri, 25 Sep 2015 22:14:04 +0000 (UTC) From: "Yusaku Sako (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-8302) Display EULA for specific stacks when available during cluster deployment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-8302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako updated AMBARI-8302: -------------------------------- Fix Version/s: (was: 2.1.2) > 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 > 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)