When deploying the shared component, the topic confirmation prompt is displaced by Terraform's "Still creating" message that's printed every 10s:
aws_sns_topic_subscription.monitoring (local-exec): To confirm the pending subscription of azul-group@ucsc.edu
aws_sns_topic_subscription.monitoring (local-exec): to the SNS topic that receives monitoring and security notifications, please
aws_sns_topic_subscription.monitoring (local-exec): open the "Subscription Confirmation" email, copy the "Confirm subscription"
aws_sns_topic_subscription.monitoring (local-exec): link address, and paste it here.
aws_sns_topic_subscription.monitoring (local-exec): URL: URL:
aws_sns_topic_subscription.monitoring: Still creating... [10s elapsed]
aws_sns_topic_subscription.monitoring: Still creating... [20s elapsed]
aws_sns_topic_subscription.monitoring: Still creating... [30s elapsed]
aws_sns_topic_subscription.monitoring: Still creating... [40s elapsed]
When deploying the shared component for the first time, the prompt is scrolled off-screen almost immediately due to the flurry of other actions going on at the same time (TF has a default concurrency of 10). Once things settle, the "Still creating" prompt is the only thing printed on screen, repeatedly. We rarely need to create/update the subscription, so absent the prompt, the operator may not remember that their manual intervention is required. I certainly didn't.
When deploying the
shared
component, the topic confirmation prompt is displaced by Terraform's "Still creating" message that's printed every 10s:When deploying the
shared
component for the first time, the prompt is scrolled off-screen almost immediately due to the flurry of other actions going on at the same time (TF has a default concurrency of 10). Once things settle, the "Still creating" prompt is the only thing printed on screen, repeatedly. We rarely need to create/update the subscription, so absent the prompt, the operator may not remember that their manual intervention is required. I certainly didn't.