This message was deleted.
# general
s
This message was deleted.
n
The aws-lambda connector repo is private for now, you can try it out on StreamNative Host Cloud for now.
j
Hi @Neng, we are using the connector and would like to have access to the code for further maintenance. We could rebuild the connector but this not something we aspire and a waste of resources. Would it be possible to open the repository temporarily? Loads of appreciation is available to send your way.
n
cc @Baodi Shi could you take a look at this request?
@Jeroen van der Wal I’m not sure if the connector can be open to public again, but any feedback or feature request would be helpful, and I can help coordinate with the team to work them.
j
Hi Neng, it's not that we need features right now but since we're currently using it in production without having access to downstream code or support is a major risk. Would opening the last publicly released version to the community be an option? Can you help out @sijieg?
s
@Jeroen van der Wal Let me discuss with the team.
🙏 1
j
Hi @sijieg or others at StreamNative, is there any news on the
pulsar-io-aws-lambda
repository? I know other community members also rely on other StreamNative connectors like: • pulsar-io-google-pubsub • pulsar-io-bigquery • pulsar-io-snowflake • pulsar-io-amqp-1-0 • pulsar-io-aws-eventbridge • pulsar-io-cloud-storage • pulsar-io-lakehouse • pulsar-io-sqs • pulsar-io-iotdb • pulsar-io-activemq • pulsar-io-huawei-function-graph-connector • pulsar-io-http-connector • pulsar-io-huawei-dis • pulsar-io-huawei-lts-connector • pulsar-io-huawei-obs-connector • pulsar-io-pulsar-connector I hope you are committed keeping them available to the community or allow the community to take ownership. The same goes for protocol handlers (kafka, mqtt, etc). Looking forward to a response.