geoffreywiseman / oldamis Goto Github PK

Some source lines are getting long, and my test accounts are by no means large accounts.

Honestly, very large accounts may not want sources listed at all, or only for not-ok cases, but ... I can revise that if I get users who complain.

In the same way that a 1yo AMI is marked in yellow (warning), it might be good to mark an AMI that is has a deprecation time and that time isn't too far into the future (say, within a month?).

Need to republish to NPM.

If credentials aren't available, should get a better error message.

Once we have a test, we should run the test in GHA. Shouldn't take much.

The usual format, link to the usual place for now. Could do something more automated, but ... not yet.

Having at least one jest test that mocks AWS should make it a little easier to move towards a fully tested codebase if I make further revisions.

The AWS SDK supports paginated reading in a way that might be easier than what I've already done.

It's not a big deal, but its worth trying the other approach and, if it seems cleaner/easier/better, sticking with that.

https://aws.amazon.com/blogs/developer/pagination-using-async-iterators-in-modular-aws-sdk-for-javascript/

Publish to NPM when merge to main or when tagged on main? Would need to store credentials in GHA.

Consider tools like:

• release-it
• semantic-release

etc

What if someone wants to know about old AMIs, but has a different take on what "old" should be? 18 months? two years? six months? Is this something anyone cares about?