Configmaps for services other than s3 missing

[jgryszko]

Is it planned to create config maps for other services than s3 (sqs, sns ...), or is there any reason, why it was omitted? Looking for areas to contribute...

[christopherhein]

There is not a reason, this would be a great first issue :)

[ivanich]

@christopherhein Any update on this? I've tried to add corresponding additional resource to sqsqueue.yaml model and rebuild aws-service-operator but it still doesn't create configmap for sqs. Basically what I tried so far:

  additionalResources:
    configMaps:
    - name: sqsCM
      data:
      - key: queueARN
        value: "{{.Obj.Output.QueueARN}}"
      - key: queueName
        value: "{{.Obj.Output.QueueName}}"
      - key: queueURL
        value: "{{.Obj.Output.QueueURL}}"

and then run "make rebuld" to regenerate and build code. Am I miss something?

[ivanich]

Turned out it never used my edited code but used unmodified sources from vendor dir.

[christopherhein]

Turned out it never used my edited code but used unmodified sources from vendor dir.

So you have it working?

[ivanich]

Turned out it never used my edited code but used unmodified sources from vendor dir.

So you have it working?

Yes, for some reason sources from vendor/github.com/awslabs/aws-service-operator/ was used. It would be nice to see configmap support for all resources in upstream as well as helm charts repo.