Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Michael Gerlach
    @n3ph
    please close terraform-providers/terraform-provider-aws#255
    Michael Gerlach
    @n3ph
    please close terraform-providers/terraform-provider-aws#1249
    Michael Gerlach
    @n3ph
    please close terraform-providers/terraform-provider-aws#4104
    Michael Gerlach
    @n3ph
    please close terraform-providers/terraform-provider-aws#1655
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#2841 can be closed as a duplicate
    I think terraform-providers/terraform-provider-aws#353 can be closed
    Michael Gerlach
    @n3ph
    please close terraform-providers/terraform-provider-aws#2945
    duckfez
    @duckfez
    @bcornils how long are you willing to wait on a response from the author of an issue if there's no response to followup requests?
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#531 can be closed
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#619 can be closed
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#582 can be closed
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#1665 can be closed
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#2144 can be closed
    terraform-providers/terraform-provider-aws#2841 can be closed
    Kit Ewbank
    @ewbankkit
    terraform-providers/terraform-provider-aws#2695 can be closed
    bfuller
    @bcornils
    @duckfez well vacations this time of year so it's hard to say
    i'd give a few weeks
    i don't know their history for example are they deployed someone
    So I'd say 2 weeks and close or move forward
    duckfez
    @duckfez
    :thumbsup:
    Tom Elliff
    @tomelliff
    I just went to answer terraform-providers/terraform-provider-aws#5059 but then realised it looks like terraform-providers/terraform-provider-aws#4942 was closed instead of merged so the docs haven't been updated with the alternative yet
    I think it was accidental in the insane amount of work @bflad and others had to do that day but let me know if anything needs changing about it
    that issue can probably be closed as well
    Brian Flad
    @bflad
    Yikes! Thanks for reporting that. Actually merged it :sweat_smile:
    Tom Elliff
    @tomelliff
    thanks :)
    Brian Flad
    @bflad
    Funny enough, I just ran back across your PR terraform-providers/terraform-provider-aws#3535 which we can get in if the retry timeout is reasonable
    just needs rebase :)
    Tom Elliff
    @tomelliff
    terraform-providers/terraform-provider-aws#5146 can be closed I think
    Alice
    @alice-sawatzky
    sorry if this isn't the right place to ask about PRs. any chance someone can look at hashicorp/terraform#18533 ?
    Tom Elliff
    @tomelliff
    terraform-providers/terraform-provider-aws#5351 can be closed as a duplicate of terraform-providers/terraform-provider-aws#5344 I think
    Andrew Bobulsky
    @RulerOf
    Hey guys. I'm over here from the Lobby where people typically ask all their questions. Sometimes people come in with questions about provider maintenance pull requests and those usually go unresolved. Should I send them over here instead?
    Or is there a better place for provider-specific discussion? My assumption is that it's all based in github but i could be wrong
    bfuller
    @bcornils
    this is a good place for provider specific.
    Andrew Bobulsky
    @RulerOf
    Okay. I'll suggest people who come in with questions that are developing providers try their luck in here if no one has answers to their questions then.
    bfuller
    @bcornils
    yes please. I monitor it. I just happened to be on PTO so apologies for the delay
    Andrew Bobulsky
    @RulerOf
    No problem! Thanks :)
    Kit Ewbank
    @ewbankkit
    Kit Ewbank
    @ewbankkit
    Tom Elliff
    @tomelliff
    I've started taking a look at the DLM resource this morning after being busy for a few weeks but after quickly hacking together a loose stab at it I'm getting a date parsing error when trying to decode the JSON response from the SDK. I'm not doing anything with the date yet but the DLM API returns the created/modified times but that's all inside the SDK, not my code. Am I missing something here? I can't see any issues on the Go SDK Github repo about this
    when I apply my resource I get:
    * aws_dlm_lifecycle_policy.example: 1 error(s) occurred:
    
    * aws_dlm_lifecycle_policy.example: SerializationError: failed decoding JSON RPC response
    caused by: parsing time "2018-08-13T11:49:27+0000" as "2006-01-02T15:04:05Z": cannot parse "+0000" as "Z"
    Tom Elliff
    @tomelliff
    any maintainers/people who actually write Go more than once every couple of months able to help me debug why my new resource (terraform-providers/terraform-provider-aws#5558) doesn't properly refresh state for the nested policy_details config?
    don't get any panics/errors in the logs when refreshing, it just seems to ignore things so I must have missed something obvious
    J. Taylor Mayfield
    @jtaylormayfield
    Decided to give my own issue a go (terraform-providers/terraform-provider-aws#5656). I'm trying to figure out how to generate the hard-coded resource ID used in the acceptance tests. In my case, I'm trying to figure out how to determine the resource ID for aws_codebuild_project.artifacts block.
    Tom Elliff
    @tomelliff
    have you pushed your code to your fork so we can see what you've tried?
    J. Taylor Mayfield
    @jtaylormayfield
    No I haven't. I have this thing about pushing code before the test is green :)
    Tom Elliff
    @tomelliff
    you can always rebase your changes afterwards and just commit it as a WIP commit
    otherwise it's difficult for people to be able to help you if they can't see your code :)