Github user jmlogan commented on the issue:
https://github.com/apache/nifi/pull/3187
I can close it but I was wondering how the SDK derives that list ...it
looks like it's just an enum on their side -- what about regions that
aren't in that enum? It seems like this still might be a problem for these
regions. I would imagine this is a problem that users have ran into, and
isn't being addressed in either PR.
On Thu, Nov 29, 2018 at 4:35 AM Sivaprasanna <[email protected]>
wrote:
> *@zenfenan* commented on this pull request.
>
> As discussed in the original user mails thread, this custom enum on the
> NiFi side has to go. I raised the PR #3190
> <https://github.com/apache/nifi/pull/3190> addressing the same. With
> that, we don't have to update our enum every time there is a change.
>
> @jmlogan <https://github.com/jmlogan> Mind closing this one? If the
> intention is to have the new region added then we can update the SDK
> version in the POM which would bring the latest available regions
> automatically without even having the enum.
>
> â
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/nifi/pull/3187#pullrequestreview-179698941>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ACILCV9sm6Poq--SUiCmjE6gAth3NHeRks5uz6pRgaJpZM4Y3_UK>
> .
>
---
