I think I have this resolved.
the certname was in fact the solution. I had a permissions problem that
looked like things weren't working correctly. Once I got that straightened
out the value passed into my ENC script (vpc-id plus hostname) worked fine.
Thanks
On Thu, Feb 27, 2014 at 4:19 PM, Pat
On Fri, Feb 28, 2014 at 8:57 AM, John Pyeatt wrote:
> I am trying to use one puppetmaster to support multiple AWS VPCs. In other
> words, I am trying to have one puppetmaster support multiple independent
> networks.
>
> The problem with this is that it is possible for machines on two different
> V
See comments below.
On Thu, Feb 27, 2014 at 4:45 PM, Christopher Wood <
christopher_w...@pobox.com> wrote:
> (inline)
>
> On Thu, Feb 27, 2014 at 03:57:21PM -0600, John Pyeatt wrote:
> >I am trying to use one puppetmaster to support multiple AWS VPCs. In
> other
> >words, I am trying to
(inline)
On Thu, Feb 27, 2014 at 03:57:21PM -0600, John Pyeatt wrote:
>I am trying to use one puppetmaster to support multiple AWS VPCs. In other
>words, I am trying to have one puppetmaster support multiple independent
>networks.
>
>The problem with this is that it is possible fo
I am trying to use one puppetmaster to support multiple AWS VPCs. In other
words, I am trying to have one puppetmaster support multiple independent
networks.
The problem with this is that it is possible for machines on two different
VPCs to have the same hostname/ipaddress.
I use an ENC script on
