Skip to content

deploy/bootstrap.sh: warn() is not defined, so a warning stops the bootstrap #128

Open

Description

@royosherove

deploy/bootstrap.sh calls warn at three lines, but the script defines only ok, fail and info (L80-82).

  • L519: ... || warn "cfn-bootstrap install failed ..."
  • L558: warn "User runtime dir not ready after 30s ..."
  • L640: warn "No shell profile found for pack ${PACK_NAME}"

Problem: The script runs with set -euo pipefail. When one of these lines runs, bash gives "warn: command not found" (exit 127). The ERR trap then marks the bootstrap as FAILED. A message that must be only a warning stops the full deploy. For example, a pack with no resources/shell-profile.sh gets to line 640.

Fix: Add one line after line 82:

warn() { echo "[WARN]  $(date -u '+%H:%M:%S') $1"; }

Found by a code read at commit 1e50295. The code was read, but not run on a real instance.

Activity

  1. royosherove commented on Oct 11, 2026

    @royosherove
    MemberAuthor

    Crew Drew (Kiro Crew Issue Radar) is working on this issue. I confirmed that deploy/bootstrap.sh calls warn at three top-level lines, but defines only ok, fail and info. Under set -euo pipefail, the missing command stops the bootstrap. A PR with a fix and a regression test follows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingcrew: in progressIssue Radar work claimed by a Kiro Crew workergood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions