By using AWS re:Post, you agree to the Terms of Use

Unanswered Questions tagged with DevOps

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

CodeBuild Bug? AWS CLI broken on AL2/aarch64 env, error "pyenv: version `3.9.7' is not installed"

## Summary: On CodeBuild projects running on AL2/aarch64, running the `aws` CLI command (any command works, I use `--version` as a sanity check) yields the following error: ``` [Container] 2022/09/10 02:39:37 Running command aws --version pyenv: version `3.9.7' is not installed (set by /codebuild/output/src576940877/src/.python-version) ``` The process exits with status code 1 and the build terminates. I can reproduce the error exactly on my M1 MBP running locally, following the instructions for local agent usage [here](https://docs.aws.amazon.com/codebuild/latest/userguide/use-codebuild-agent.html). ## Steps to Reproduce 1. Create minimal buildspec.yml: ```yml version: 0.2 phases: build: commands: - aws --version ``` 2. Launch on CodeBuild project set to AL2/aarch64, on SMALL size build. ## Expected behavior Build should pass. Output of command should be: ``` [Container] 2022/09/10 03:00:41 Running command /usr/local/bin/aws --version aws-cli/2.7.31 Python/3.9.11 Linux/5.10.104-linuxkit exe/aarch64.amzn.2 prompt/off ``` ## Actual behavior Output is actually: ``` [Container] 2022/09/10 02:39:37 Running command aws --version pyenv: version `3.9.7' is not installed (set by /codebuild/output/src576940877/src/.python-version) ``` ## Workaround The AWS CLI can be installed manually and run via direct path: ``` version: 0.2 phases: install: runtime-versions: python: 3.9 commands: - curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip" - unzip awscliv2.zip - ./aws/install build: commands: - /usr/local/bin/aws --version ``` This produces the expected output and the build succeeds.
0
answers
0
votes
20
views
asked 15 days ago

Lexbot not eliciting all slot values in conversation

I'm trying to automate the process of creating a lexbot that receives slot values and processes them in a lambda function. The creation of the bot and functions are completed and fine, when I check the amazon lex console, the bot has been created, the intents are correct and the slot elicitations are there. However, when I run the bot and type an utterance, the bot goes straight to fulfilment lambda function as opposed to asking for the other slot values. All the slots have the slot constraint 'required', I'm just not sure why they are not being elicited by the bot. I will attach the json response from list_slots below: ![json response of list slots](/media/postImages/original/IMzBaosX9_QYWsel9MzYy8tQ) Below I will attach images of the bot specifications from the console. ![slot values](/media/postImages/original/IM4GGdRJpRQgqML7zXFSxlCA) ![shows the lambda function is called on fulfillment](/media/postImages/original/IMdjLiIZ32TqyaBpVplSnN8Q) ![Example of test output](/media/postImages/original/IM6u9Bp-ruQ22K-CXsN43bzA) I will also attach the content of the boto3 request I used to create the the slot in the first place. ![Example of the boto3 request used to create the slot](/media/postImages/original/IMauJP2jvYRu6dPSBpUkKxEA) The following is an image of my intent, to show that the fulfilment code hook is enabled: ![Code that shows the creation of the intent](/media/postImages/original/IMkSN5QrZaSymUBAX29f0R7w) My question is, why is the bot not asking for the other slot values when all the configuration suggests it should do otherwise?
0
answers
0
votes
29
views
asked a month ago