AWS AppFlow Flow renders PANIC into docs

[t0yv0]

What happened?

Another example of PANIC in docs.

Example

resource "aws_appflow_flow" "example" {
# ... other configuration ...

trigger_config {
scheduled {
schedule_expression = "rate(1minutes)"
}
}
}

to

package generated_program;

import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.appflow.Flow;
import com.pulumi.aws.appflow.FlowArgs;
import com.pulumi.aws.appflow.inputs.FlowTriggerConfigArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;

public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }

    public static void stack(Context ctx) {
        var example = new Flow("example", FlowArgs.builder()        
            .triggerConfig(FlowTriggerConfigArgs.builder()
                .scheduled(%!v(PANIC=Format method: runtime error: invalid memory address or nil pointer dereference))
                .build())
            .build());

    }
}

Output of pulumi about

N/A

Additional context

N/A

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).