Fix metadata server path resolution issues #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes three path resolution errors that prevented the metadata server from starting properly.
Changes
'../lib/metadata-server.js'to'../metadata-server.js''../'to'../../../../'to properly resolve to project root'../service'to'../../../../service'These paths must resolve correctly from the
dist/src/lib/handlers/directory context after TypeScript compilation.Testing Instructions
npm run buildnode dist/src/bin/alks.js server startcurl http://169.254.169.254/latest/meta-data/iam/security-credentials/alkscurl http://169.254.169.254/latest/meta-data/iam/security-credentials/alksNote: Testing must use
169.254.169.254(not127.0.0.1:45000) as the pf rules redirect traffic.Related