Return-Path: X-Original-To: apmail-aurora-issues-archive@minotaur.apache.org Delivered-To: apmail-aurora-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8360107D9 for ; Wed, 9 Sep 2015 19:13:07 +0000 (UTC) Received: (qmail 7619 invoked by uid 500); 9 Sep 2015 19:12:45 -0000 Delivered-To: apmail-aurora-issues-archive@aurora.apache.org Received: (qmail 7574 invoked by uid 500); 9 Sep 2015 19:12:45 -0000 Mailing-List: contact issues-help@aurora.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.apache.org Delivered-To: mailing list issues@aurora.apache.org Received: (qmail 7565 invoked by uid 99); 9 Sep 2015 19:12:45 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Sep 2015 19:12:45 +0000 Date: Wed, 9 Sep 2015 19:12:45 +0000 (UTC) From: "Jake Farrell (JIRA)" To: issues@aurora.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AURORA-1485) TaskConfig default container value breaks client library generation for GO MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jake Farrell created AURORA-1485: ------------------------------------ Summary: TaskConfig default container value breaks client library generation for GO Key: AURORA-1485 URL: https://issues.apache.org/jira/browse/AURORA-1485 Project: Aurora Issue Type: Story Components: Client Reporter: Jake Farrell Assignee: Jake Farrell Fix For: 0.10.0 When generating the client api library for go the default containerizer used as a hack for AURORA-1185 breaks and causes the client lib to not be generated correctly. The default value for the optional field `container = { "mesos": {} }` is not necessary as it is defaulted in java code on the api side. Tracking this down it looks like the default value was a last minute addition based on some review comments and is not necessary or used anywhere. Removing the default value does not impact anything. -- This message was sent by Atlassian JIRA (v6.3.4#6332)