黄瓜与内置测试？(Cucumber vs. built-in testing? [Rails])

 当我问自己同样的问题时，“我可以使用配置器的输出来输入另一个资源的变量吗？”，我找到了答案。 
 
 在这个时候，提供者的结果只是简单地传输到terraform的标准中，而不会被捕获。 
 
 鉴于您在两个节点上运行远程供应商，并且您尝试访问S3中的值 - 我同意这种方法，我也会这样做 - 您可能需要做的是处理脚本中的竞争条件使用sleep命令，或通过调度脚本稍后使用at或cron或类似的调度系统运行。 
 
 一般来说，Terraform想要预先访问所有变量，或者作为提供者的结果。 提供者不一定被视为Terraform中的头等舱。 我不在核心团队，所以我不能说为什么，但我的推测是，它会降低复杂性，忽略成功或失败以外的预设结果，因为提供者只是脚本，因此他们的结果通常是非结构化的。 
 
 如果您需要更多的增强功能来设置您的实例，我建议一个专门的工具来实现此目的，比如Ansible，Chef，Puppet等。Terraform的重点确实在于基础设施，而不是软件组件。 

When I asked myself the same question, "Can I use output from a provisioner to feed into another resource's variables?", I went to the source for answers.
 
At this moment in time, provisioner results are simply streamed to terraform's standard out and never captured.
 
Given that you are running remote provisioners on both nodes, and you are trying to access values from S3 - I agree with this approach by the way, I would do the same - what you probably need to do is handle the race condition in your script with a sleep command, or by scheduling a script to run later with the at or cron or similar scheduling systems.
 
In general, Terraform wants to access all variables either up front, or as the result of a provider. Provisioners are not necessarily treated as first-class in Terraform. I'm not on the core team so I can't say why, but my speculation is that it reduces complexity to ignore provisioner results beyond success or failure, since provisioners are just scripts so their results are generally unstructured.
 
If you need more enhanced capabilities for setting up your instances, I suggest a dedicated tool for that purpose like Ansible, Chef, Puppet, etc. Terraform's focus is really on Infrastructure, rather than software components.