On 12 April 2016 at 20:04, R.I.Pienaar <r...@devco.net> wrote:
>
>
> ----- Original Message -----
>> From: "dean" <dean.wil...@gmail.com>
>> To: "puppet-dev" <puppet-dev@googlegroups.com>
>> Sent: Tuesday, 12 April, 2016 20:56:09
>> Subject: Re: [Puppet-dev] Re: The Future of Puppet [Was: Deprecation logs]
>
>> On 12 April 2016 at 19:16, Ryan Whitehurst <r...@puppet.com> wrote:
>>
>>> The puppetlabs-aws module [1] is pretty powerful these days -- we on
>>> the operations team here at Puppet use it for managing a large portion
>>> of our AWS infrastructure.
>>
>> If you remove the Route53 DNS record resource types then that module
>> claims to support about 21 AWS services. Terraform supports about 130
>> in the currently released version. And that'll increase in the next
>> release as their new service adoption rate is staggering to watch.
>> Even Ansible has over 50 AWS resource management modules. Some of the
>> gaps are pretty high in the environment bootstrapping order too - IAM
>> roles for example. If I went puppet-aws as my tool of choice I can't
>> even add other IAM users without going back outside my config
>> management. This isn't just a rush to add new services either, those
>> are more mature services that have been around for a long while.
>>
>> I can see how for lift and shift AWS deployments you can get quite far
>> with the instance and networking types puppet-aws provides but if
>> you're looking to embrace AWS as a platform it very quickly loses out
>> in comparable features. There might also be an issue here for how
>> difficult it is to write a solid puppet type and provider but I'm not
>> fairly placed to answer that.
>
> Every time I try to play with the puppet aws resources I end up wanting
> to reference data in other resources and cant.
>
> resource "aws_instance" "web" { .... }
>
> resource "aws_elb" "myapp" {
> ...
> instances = ["${aws_instance.web.id}"]
> }
>
Quick correction, mainly unrelated to the main thread. The AWS module
uses the puppet name for reference, you never have to deal with the ID
directly. So the following should just work.
resource "aws_instance" "web" { .... }
resource "aws_elb" "myapp" {
...
instances = ["web"]
}
Gareth
> I do not think you can do this with the Puppet resources - couldn't when
> I last looked but something could have changed as it's been a while
>
> This is quite a common pattern with AWS since the stuff is very inter
> connected and cross referenced.
>
> Is there a solution with the puppet modules for this?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/2021155169.607149.1460487846366.JavaMail.zimbra%40devco.net.
> For more options, visit https://groups.google.com/d/optout.
--
Gareth Rushgrove
@garethr
devopsweekly.com
morethanseven.net
garethrushgrove.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/CAFi_6yLn4HoJZ9s03PR_z6mbR5P8R17J%3Db41d8db4zykPoqCgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
