Bug: variable typo base54val should be base64val in pkg/aws/ec2.go

[SeanHaimovich]

There is a variable typo in pkg/aws/ec2.go around lines 55-56.

The variable is named base54val, but it stores the result of
base64.StdEncoding.EncodeToString(), so it should be named base64val.

File: pkg/aws/ec2.go, lines 55-56
Expected fix: rename base54val to base64val everywhere it is used.

(Filed at a maintainer's request as part of validating the automated
review workflow on bot-opened PRs.)

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 11:39 AM UTC · Completed 11:41 AM UTC
Commit: 37b10e4 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Severity: Low · Category: Bug (cosmetic typo)

Problem

The variable base54val in pkg/aws/ec2.go (lines 56–57) is a typo — it stores a base64-encoded value and should be named base64val. The code works correctly; only readability is affected.

Verified

The typo has been confirmed in the current source. The variable appears twice in the same block:

• Line 56: assignment from base64.StdEncoding.EncodeToString()
• Line 57: taking the address with &base54val

Recommended Fix

Rename base54val → base64val on both lines. No behavioral change expected.

Proposed Verification

# After the rename:
make build   # compilation succeeds
make test    # all existing tests pass
make lint    # no lint regressions

This is a good first issue — straightforward rename with no functional risk.

---

Labels: This is a confirmed cosmetic bug (variable typo) that is trivial to fix, matching the 'bug' and 'good first issue' labels.

[coder-bigwig]

Hi, I'm new to open source and I'd like to work on this issue. I noticed the note about validating the automated review workflow on bot-opened PRs. Is it okay for me to submit a manual PR for this fix?

[SeanHaimovich]

Hi, thanks for asking first. This particular issue was filed specifically to validate the automated coder-bot workflow end to end (that's the note you spotted), so we'd like to leave this one for the bot to pick up. Sorry for the tease with the good-first-issue label. If you're looking to contribute to this project, the maintainers' other open issues are the place to look, and asking before starting like you did here is exactly the right instinct.

[coder-bigwig]

Thanks for the clarification! I understand. I'll look for another open issue to contribute to. Appreciate the guidance!