Not sure how to run .sh file in poe

[kurt-rhee]

I created a .sh file like so:

#!/bin/sh

# -e: Exit immediately if a command exits with a non-zero status.
# -u: Treat unset variables as an error when substituting.
# -o pipefail: The return value of a pipeline is the status of the last command
#              to exit with a non-zero status, or zero if no command fails.
set -euo pipefail

export AWS_CODEARTIFACT_TOKEN="$(
    aws codeartifact get-authorization-token \
    --domain xxx \
    --domain-owner xx \
    --query authorizationToken \
    --output text
)"


if [ -z "$AWS_CODEARTIFACT_TOKEN" ]; then
    echo "AWS CodeArtifact Token is empty"
    exit 1
fi

LATEST_VERSION=$(aws codeartifact list-package-versions \
    --package core \
    --domain proximal-code-artifact-domain \
    --domain-owner 016997484973 \
    --repository proximal-hub \
    --sort-by PUBLISHED_TIME \
    --format pypi \
    --output text \
    --query 'versions[0].version' \
    )

export UV_INDEX_PROXIMAL_USERNAME=aws
export UV_INDEX_PROXIMAL_PASSWORD="$AWS_CODEARTIFACT_TOKEN"

uv add "core==$LATEST_VERSION" --index proximal

in pyproject.toml

[tool.poe.tasks]
core = "source _scripts/update_core.sh"

execution via poe

(api) kurt@Mac api % poe core
Poe => source _scripts/update_core.sh
  × No solution found when resolving dependencies:
  ╰─▶ Because core was not found in the package registry and your project depends on core==0.1.5, we can
      conclude that your project's requirements are unsatisfiable.

      hint: An index URL
      (https://proximal-code-artifact-domain-016997484973.d.codeartifact.us-east-2.amazonaws.com/pypi/proximal-hub/simple/)
      could not be queried due to a lack of valid authentication credentials (401 Unauthorized).

execution via source _scripts/update_core.sh everything works as expected

[nat-n]

Hi @kurt-rhee,

The error you shared looks like it's coming from uv, before even running the task. Normally Poe the Poet detects that you're using it within a uv project, and then runs tasks via uv run to benefit from all the dependencies available in your project environment. Normally this is a good idea, but since this task looks like it's intended to be run as part of the initial setup before uv is useable in your project you can disable this by directing poe to ignore uv and use a "simple" executor for this task by setting the execution option like so:

[tool.poe.tasks.core]
cmd = " <task content does here> "
executor = { type = "simple" }

However there's another surface level issue with your task definition which is that by default poe tasks run as subprocesses without a shell (unless your specify the shell task type), and there probably isn't an executable called source on your path (normally it's a shell built-in).

To run a shell script as a task, you can do one of:

1. Create cmd task to call the shell script:

   [tool.poe.tasks.core]
   cmd = "./_scripts/update_core.sh"

2. Implement a shell task) :

   [tool.poe.tasks.core]
   shell = """
   # inline the shell script here
   """

However it looks like maybe your script is actually intended for initializing the environment in your current shell? which isn't an ideal fit for a task runner (which in principle can't modify the parent shell).

So you could approach this in one of two ways:

1. Create a cmd task that creates a new shell after sourcing the script, and then creates another child shell for the user to interact with (unfortunately you can't do this with a shell task because they don't support interactive mode).

   [tool.poe.tasks.core]
   cmd = """
   $SHELL -c "
   source ./_scripts/update_core.sh; # could also inline your export statements etc here
   exec $SHELL;"
   """

2. Refactor your setup logic into poe config (this might be overkill)

   [tool.poe.tasks._get_ca_token] # underscore prefix makes the task hidden from the CLI
   cmd = """
   aws codeartifact get-authorization-token
       --domain ${CA_DOMAIN}
       --domain-owner ${CA_DOMAIN_OWNER}
       --query authorizationToken
       --output text
   """
   args = [ # optionally you can make the task configurable with arguments like so
     { name = "CA_DOMAIN", default = "xx" },
     { name = "CA_DOMAIN_OWNER", default = "xx" },
   ]
   
   [tool.poe.tasks._get_core_latest_version]
   cmd = """
   aws codeartifact list-package-versions
    --package core
    --domain proximal-code-artifact-domain
    --domain-owner 016997484973
    --repository proximal-hub
    --sort-by PUBLISHED_TIME
    --format pypi
    --output text
    --query 'versions[0].version'
   """
   
   [tool.poe.tasks.core]
   help = "Add dependency on latest version of core"
   cmd  = "uv add \"core==${LATEST_VERSION}\" --index proximal"
   env  = { UV_INDEX_PROXIMAL_USERNAME = "aws" }
   uses = { LATEST_VERSION = "_get_core_latest_version", UV_INDEX_PROXIMAL_PASSWORD = "_get_ca_token" }
   
   [tool.poe.tasks.shell]
   help = "Create a new shell with codeartifact access"
   cmd  = "$SHELL"
   env  = { UV_INDEX_PROXIMAL_USERNAME = "aws" }
   uses = { UV_INDEX_PROXIMAL_PASSWORD = "_get_ca_token" }

I haven't tested any of this but you get the idea. See docs on task dependencies