Stefan Fussenegger
Stefan Fussenegger
Document uses of eureka appName, vipAddress, with regards to spring cloud uses of serviceId, etc...
`EurekaDiscoveryClient.getIntsances(String)` doesn't use the `serviceId` or application name but the VIP Address to lookup instances: ```!java public List getInstances(String serviceId) { List infos = this.eurekaClient.getInstancesByVipAddress(serviceId, false); List instances = new...
[assuming roles](http://docs.aws.amazon.com/STS/latest/APIReference/API_AssumeRole.html) is another way to authenticate. `ContextCredentialsAutoConfiguration` could check for `cloud.aws.credentials.roleArn` and `cloud.aws.credentials.roleSessionName` and wrap the `AWSCredentialsProvider` created in `ContextConfigurationUtils.registerCredentialsProvider(..)` with a `STSAssumeRoleSessionCredentialsProvider`
It would be great to have an optional log for updated data. This could be used to trigger further processing of updates. This could be something as simple as a...
go-e support is currently limited to the [Local HTTP API](https://github.com/goecharger/go-eCharger-API-v2/blob/main/http-en.md). As far as I understand it the [Cloud HTTP API](https://github.com/goecharger/go-eCharger-API-v2/blob/main/cloudapi-en.md) is largely the same. Currently, there are 2 main methods...