TIBCOSoftware / TIBCOSoftware/be-contribution
KinesisChannel - The AWS configurations should not be dependent on host machine.
Open
@rkhera-tibco is already working on this.
Since Jun 3, 2023.
bug
Kinesis channel
- Dominant language
- Java
- Stars
- 0
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Version Information
| Software | Version(s) |
|---|---|
| BusinessEvents | 5.6.1 |
| OS Type? | |
| OS Version? |
Description
Currently, the AWS profile setup has to be done on the host machine where the engines are supposed to be run. Since we already provide credentials and other information in the project itself, there should not be any need to configure the information in the machine.
We should be able to run CDD and EAR from any machine without doing a profile setup.
<property-group comment="" name="kinesis">
<property name="tibco.clientVar.kinesis/access.key" type="String" value="xyxyxyxyxyxyxyyyyyy"/>
<property name="tibco.clientVar.kinesis/secret.key" type="String" value="xyzxyzyzyzyyzyzyzyzyzyzyzyzyzyz"/>
<property name="tibco.clientVar.kinesis/profile.name" type="String" value="test"/>
<property name="tibco.clientVar.kinesis/stream.name" type="String" value="StockTradeStream"/>
<property name="tibco.clientVar.kinesis/application.name" type="String" value="StockTradeProcessor"/>
<property name="tibco.clientVar.kinesis/region.name" type="String" value="us-east-1"/>
<property name="tibco.clientVar.kinesis/max.records" type="Integer" value="3"/>
</property-group>
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.