Fork me on GitHub
#aws
<
2020-03-20
>
kenny16:03:52

The information in the endpoints.edn file is extremely useful. We've been depending on it in many of our specs for aws resources. Is the format in this file something we should be depending on?

dchelimsky16:03:51

@U083D6HK9 we won't guarantee it's format at this point, as it's sourced from aws

kenny16:03:52

Ah. That seems unlikely to change.

dchelimsky16:03:17

Agreed, but there is nobody committing to that (not aws, not cognitect).

dchelimsky16:03:08

That said, if you think there's a good case to be made for an endpoints API, please feel free to submit an issue. We'd be happy to discuss it, at the very least.

kenny16:03:29

Depending on it seems better than having to manually write & update these specs. To be clear, I'm not necessarily after an endpoints API, per se. We are using the data in that file to create specs for AWS partitions, services, services in a region, regions in a partition, etc.

kenny16:03:09

Having these sort of specs built into aws-api could be useful but potentially a non-goal for the project.

dchelimsky16:03:28

But if you're using it for something broadly applicable, it's worth some thought.

1
dchelimsky16:03:44

Even if not for aws-api, but for a separate project.