https://docs.google.com/spreadsheets/d/1eKvykNRsUk1v32IeOqbvPaml2PukcvqXtKX2SzOxdE0/edit#gid=0
* 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"
policy_details
config?
aws_codebuild_project.artifacts
block.
anyone experienced with building custom terraform plugins in go?
im trying to modify an existing plugin to login to the 3rd party upon resource creation so I can take advantage of data source outputs. The issue I have is that there is a race condition between the login to datadog while the resource is attempting creation.
https://github.com/terraform-providers/terraform-provider-vault/issues/219#issuecomment-435622604
would be nice if there was a a blog post or custom provider skeleton that implements MyClient correctly to avoid the race condition. I did find this but no client implementation so far besides digging through other providers. https://github.com/pyToshka/terraform-provider-skeleton
availability_zones
doesn't conflict with vpc_zone_identifier
in the aws_autoscaling_group
resource? I can see terraform-providers/terraform-provider-aws@e772e54 where you added a comment in the docs suggesting that they shouldn't be used at the same time but I can't see why it doesn't just straight conflict in the schema similar to security_groups
and vpc_security_group_ids
on the aws_instance
resource?