TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

CloudAMQP experiences ops nightmare today

2 点作者 bigsassy超过 10 年前

2 条评论

DrJ超过 10 年前
So I just read this, the CEO added the below<p><pre><code> insts = [ @ec2.instances.with_tag(&#x27;Name&#x27;, &quot;CloudAMQP-#@name0*&quot;).to_a, @ec2.instances.with_tag(&#x27;Name&#x27;, &quot;CloudAMQP-#@name-*&quot;).to_a, @ec2.instances.with_tag(&#x27;Service&#x27;, &#x27;CloudAMQP&#x27;).with_tag(&#x27;Name&#x27;, &quot;#@name-*&quot;).to_a, ].flatten </code></pre> unless they have a variable named &quot;@name0&quot; that first line would&#x27;ve evaluated to &quot;CloudAMQP-*&quot;, which would then have the fun happen.
bigsassy超过 10 年前
CloudAMQP&#x27;s CEO&#x2F;CTO from the support chat room:<p><pre><code> Yes, it seems to have been a bug in our instance deletion code, that deleted all instances in that region, instead of one. This of course is a disaster</code></pre>