Add support for complex data types

[tsahiduek]

Feature Description

Problem Statement:
For complex objects, such as ACK DyanmoDB Table definition, there's a need to define a complex data-types that will be used as an input for the ResourceGroup.
As an example, ACK DynamoDB Table gets as an input, a list of the following struct:

 attributeDefinitions:
    - attributeName: id
      attributeType: S
    - attributeName: name
      attributeType: S

Currently there's no way to define the following:

tableElement: map[string][string]
attributeDefinition: []tableElement

Proposed Solution:
support complex data types to be able to pass those as an input to the ResourceGroup spec values.

Alternatives Considered:
none

Additional Context:
none

• Please vote on this issue by adding a 👍 reaction to the original issue
• If you are interested in working on this feature, please leave a comment

[franckyvrac]

I've got the same problem to define list of protocols and ports in an networkpolicy :

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: np
spec:
  egress:
  - ports:
    - port: 21
      protocol: TCP
    - port: 25
      protocol: TCP
    - port: 80
      protocol: TCP
    - port: 443
      protocol: TCP