Skip to content
TheChatArchiveThe Chat Archive
Geminigemini-2.5-flash-preview-04-17· GoogleHugging Face LMArena Human Preference 140K

resource "awscloudwatcheventrule" "dailylambdatrigger" { name = var.rulename description…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with MiniMaxminimax-m1’s answer.
  1. User

    resource "aws_cloudwatch_event_rule" "daily_lambda_trigger" { name = var.rule_name description = var.rule_description schedule_expression = var.schedule_expression is_enabled = true }

    is the "is_enabled" realy depracted

  2. Gemini Assistant

    No, the is_enabled argument for the aws_cloudwatch_event_rule resource in the Terraform AWS provider is not deprecated.

    It is a standard and current argument used to control whether the EventBridge (CloudWatch Events) rule is active or disabled.

    • is_enabled = true (or omitting it, as true is the default) means the rule will fire when its schedule or event pattern is matched.
    • is_enabled = false means the rule is disabled and will not fire.

    You can find this confirmed in the official Terraform AWS Provider documentation for the aws_cloudwatch_event_rule resource.

    Perhaps you were thinking of an older argument like state which was used in very old versions of the provider but has since been removed in favor of is_enabled. is_enabled is the correct and supported argument.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.