Received: by 10.224.184.73 with SMTP id cj9mr12076238qab.6.1343141272076;
        Tue, 24 Jul 2012 07:47:52 -0700 (PDT)
X-BeenThere: puppet-users@googlegroups.com
Received: by 10.224.182.147 with SMTP id cc19ls11790435qab.8.gmail; Tue, 24
 Jul 2012 07:47:46 -0700 (PDT)
Received: by 10.224.59.73 with SMTP id k9mr12048938qah.4.1343141266951;
        Tue, 24 Jul 2012 07:47:46 -0700 (PDT)
Received: by 10.224.59.73 with SMTP id k9mr12048937qah.4.1343141266941;
        Tue, 24 Jul 2012 07:47:46 -0700 (PDT)
Return-Path: <n...@puppetlabs.com>
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53])
        by gmr-mx.google.com with ESMTPS id z30si3254815qcd.3.2012.07.24.07.47.46
        (version=TLSv1/SSLv3 cipher=OTHER);
        Tue, 24 Jul 2012 07:47:46 -0700 (PDT)
Received-SPF: pass (google.com: domain of n...@puppetlabs.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of n...@puppetlabs.com designates 209.85.216.53 as permitted sender) smtp.mail=...@puppetlabs.com; dkim=pass header...@puppetlabs.com
Received: by mail-qa0-f53.google.com with SMTP id s11so1855628qaa.12
        for <puppet-users@googlegroups.com>; Tue, 24 Jul 2012 07:47:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=puppetlabs.com; s=google;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=jA1oUW56RmxNwMoVVonlHnxHk+UXd62XH0dmUq0X2w0=;
        b=KYcdsITYPD1o13cFzc5O2zUFz5mqodo/mJcsP9fA8N4tbddPk+w6yur0d+hcASz4O8
         wVKJKygGnbNeE63v8bWMSLGDhz2VQJh4cNAfjsfZ6Z2mCEQ2JapZZB3ieDDuCGa+ZxTv
         xDgA2HHc7hkhUYlFHKZO20w/olJNGcsvk5g+M=
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-gm-message-state;
        bh=jA1oUW56RmxNwMoVVonlHnxHk+UXd62XH0dmUq0X2w0=;
        b=QZomPHyoojRrSXdVpKPeFtW2OV5fFRnD1iL0ck3fH0XE/7ul+m4cLCiv4ar8mLMItM
         ZmwDAP3MdETgp9a9brD1cFDODkcOjTDPbKpjSvSwir2TbL0MUegGy0NOQy2eqRR1y6Xy
         lYEscDZCuVcWvXNVFlocE7WfePpJIhxrFTa68I1X5MuRl18xRb5cdhTBZYGcptLMi8GJ
         8NPpIQEHERKU69vG2hBbQviDwEJnhQfYvXY0AxYX/FPxvT0qnJaqGfjubKVB4C7F0KUr
         JFJF+5mk2YulN9vCVeriEgfYazCwUak3ILxNUQeJBM4Jp7X4FN0DQytdN3dEPHerEBGJ
         uRaQ==
Received: by 10.42.66.13 with SMTP id n13mr15704026ici.39.1343141266384; Tue,
 24 Jul 2012 07:47:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.138.9 with HTTP; Tue, 24 Jul 2012 07:47:25 -0700 (PDT)
In-Reply-To: <CANs+FoXyW55o_ayCvi_CYPweWD+=9byBKpi15vDFRcTPn6Z...@mail.gmail.com>
References: <CANs+FoXyW55o_ayCvi_CYPweWD+=9byBKpi15vDFRcTPn6Z...@mail.gmail.com>
From: Nan Liu <n...@puppetlabs.com>
Date: Tue, 24 Jul 2012 07:47:25 -0700
Message-ID: <CAKt_zxF+hk72_z_GACifGp22SHG6Hp7pr9xTsqdb7EL2+19...@mail.gmail.com>
Subject: Re: [Puppet Users] sshkey type purge
To: puppet-users@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkVA6D8Ugbxx0t3nIuulckxnYNcYhxwIOsG63e07VcFG8/tFnqY0N6Y6gWrYr7ixU4uhX+Z

On Mon, Jul 23, 2012 at 11:10 AM, Trevor Vaughan <tvaug...@onyxpoint.com> wrote:
> So, I'm sure this has been covered somewhere, but I can't seem to find it.
>
> Is there no 'purge' ability on the 'sshkey' type? It would be nice to
> be able to get rid of entries for hosts that are no longer present
> without actually having to write out a node declaration for each one.

Purge isn't supported for providers based on parsed file that edit
more than one target file. So purge works for host/cron, but not
sshkey/yum. To support purging, I've used a custom define resource
based on concat files (which have other pro/cons).

Thanks,

Nan