Greg Oledzki
Greg Oledzki
Correcting the info on key-pairs. I don't think they are global, see: - https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ssh-key-pair-regions/ - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html says: > You can have up to 5,000 key pairs **per Region**. (emphasis mine)
@timmolter - do you have any specific plans for how you envision this project to be maintained?
See the Continuous Integration failure in https://github.com/scapegoat-scala/scapegoat/pull/681 Let's fix it going forward.
Would it be possible to get a release from current `main`? We would appreciate a version with #183. Is there any help needed to make it happen?
#232 WIP
- The project claims compatibility with Java 8. - Yet our only CI in PRs executes against Java 11: https://github.com/knowm/XChart/blob/develop/.github/workflows/maven_on_pull_request.yml#L20 Thus we risk bringing in something which won't work with...
Current output of json4s' `matchJson` in case of changes shows just one side of the diff (i.e. expected), e.g. ``` "Changed: {"sources": "two"}" ``` It would be useful if it...
There are numerous constraints on what is a valid `sumologic_monitor` configuration. Some of these constraints seem to be enforced only by the Sumo Logic product (API backend) vs. Terraform provider....
On some failures the provider is retrying the communication to the Sumo product and fails with errors like this: ``` Error: Post "https://api.sumologic.com/api/v1/monitors?parentId=00000000005405F8&": POST https://api.sumologic.com/api/v1/monitors?parentId=00000000005405F8& giving up after 11 attempt(s)...