Add support for kinesisanalyticsv2

Is your feature request related to a problem? Please describe. When trying to scan a Flink 1.8 kinesis data analytics app created in the console I was getting this error

botocore.errorfactory.UnsupportedOperationException: An error occurred (UnsupportedOperationException) when calling the DescribeApplication operation: test2 was created/updated by kinesisanalyticsv2 SDK. Please use kinesisanalyticsv2 SDK to make changes to test2.

It seems that these apps are getting created with the v2 SDK so need the added support to scan them

Describe the solution you’d like Add a resource type for kinesis-analytics-v2 to allow scanning and action on these resources

[PratMis]

KinesisAnalyticsV2 resource type was merged

[kylejohnson514]

Hi, I looked into this a little bit, mostly regarding the possible mapping of v1 and v2 resources.

Using kinesisanalytics boto client to call list_applications will retrieve all Kinesis Analytics resources, with no way to distinguish between version 1 and version 2. Using kinesisanalyticsv2 boto client to call list_applications will retrieve all of the same resources, but will also include each resource’s runtime, which we could use to manually filter out between v1 and v2 kinesis analytics resources. Boto docs here: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/kinesisanalyticsv2.html#KinesisAnalyticsV2.Client.list_applications

So, when we want to do anything with kinesis analytics, we’d need to first make a boto client using kinesisanalyticsv2, call list_applications, then assign new clients to the resource objects running older runtime envs (i.e. SQL 1.0, Flink 1.6) to use kinesisanalytics boto clients vs. newer runtime envs (i.e. Flink 1.8) to use kinesisanalyticsv2 boto clients, and then the API calls will use the correct version.

It’s mostly manual mapping that gets messy pretty quickly. I was playing around with it a bit here , though I’m currently still running into some errors. If we needed to, we could make it work, but it wouldn’t be ideal.

All-in-all, I think an AWS request for the enumeration api to retrieve version-specific resources based on the API used (kinesisanalytics vs. kinesisanalyticsv2) would be the most straightforward approach.