Skip to content

fix(lambda): restore masked strings in WebUIUserCreationFunction - #84

Merged
royosherove merged 1 commit into
mainfrom
fix/lambda-mask-bug
Aug 16, 2026
Merged

fix(lambda): restore masked strings in WebUIUserCreationFunction#84
royosherove merged 1 commit into
mainfrom
fix/lambda-mask-bug

Conversation

@royosherove

Copy link
Copy Markdown
Member

The Lambda ZipFile in the CFN template had two literal *** artifacts from a display-mask that got baked into the file during a splice:

  • Line 1599: Password=***Password=password,
  • Line 1643: password = ***)password = generate_password()

Result: Lambda failed at import with Runtime.UserCodeSyntaxError: unmatched ')'. Custom resource WebUIUserCreationResource never completed. Stack kirocrew-7-233-stack got stuck in CREATE_IN_PROGRESS.

Fix verified:

  • python3 ast.parse on extracted ZipFile: OK (111 lines)
  • aws cloudformation validate-template: OK (38 params)
  • bash -n install.sh: OK

Broken stack has been deleted.

Two literal *** artifacts leaked into the Lambda ZipFile in PR #83:

  Line 1599: Password=***       →  Password=password,
  Line 1643: password = ***)    →  password = generate_password()

These were sanitized display masks (from a tool that redacts what looks
like secrets when rendering diffs) that got baked into the on-disk file
during a splice operation. The Lambda failed at import with
  Runtime.UserCodeSyntaxError: unmatched ')'
so the WebUIUserCreationResource never completed.

Impact: stack kirocrew-7-233-stack got stuck in CREATE_IN_PROGRESS
because CFN kept re-invoking the broken Lambda. Stack was manually
deleted; no data lost.

Verification:
- python3 ast.parse on extracted ZipFile: OK (111 lines)
- aws cloudformation validate-template: OK (38 params)
- bash -n install.sh: OK
@royosherove
royosherove merged commit 77d49d3 into main Aug 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant