Release v3.24.3 · Cox-Automotive/alks-cli

Summary

Fixes three path resolution errors that prevented the metadata server from starting properly.

Metadata server path: Changed from '../lib/metadata-server.js' to '../metadata-server.js'
Forever daemon root: Fixed from '../' to '../../../../' to properly resolve to project root
Service files path: Updated from '../service' to '../../../../service'

These paths must resolve correctly from the dist/src/lib/handlers/ directory context after TypeScript compilation.

Additional changes by Dave:

Added .npmrc to .gitignore and removed it from the repo.
Fixed the flaky metadata server. It needed exception handling.
Fixed the mac os operational setup for starting the server.
Fixed src/lib/getMetadata.ts return type to Promise<Metadata | undefined>
Created tear down and re-test from scratch testing scripts in a new scripts directory at project root. The testing scripts are focused around the metadata server.
I commented out the e2e tests since they were failing on pulling with jfrog from artifactory. I don't have time to deal with that so I will make a separate story to address that.
Updated the README.md calling out that users should be pulling alks-cli from artifactory and notes how to setup their ~/.npmrc on how to do so.
I also removed the contents of the dist/ directory from the repo and added the directory to .gitignore. Those contents should be dynamically generated every time. Build consistency is ensured by npm-shrinkwrap.json.

Build the project: npm run build
Start the metadata server: node dist/src/bin/alks.js server start
Verify server is running: curl http://169.254.169.254/latest/meta-data/iam/security-credentials/
- Should return: alks
Test full credentials endpoint: curl http://169.254.169.254/latest/meta-data/iam/security-credentials/alks
- Should return JSON with AWS credentials

Note: Testing must use 169.254.169.254 (not 127.0.0.1:45000) as the pf rules redirect traffic.