No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

is there anything I can hack away in my local packages that will just ignore the enum validation check? e.g. a way to get around this error:

```expected runtime_environment to be one of [SQL-1_0 FLINK-1_6 FLINK-1_8 ZEPPELIN-FLINK-1_0 FLINK-1_11 FLINK-1_13 ZEPPELIN-FLINK-2_0], got FLINK-1_15.```
it seems to be a local validation error and not a remote one, as the cloudformation docs are up to date, plus terraform has included the two new enum entries