Skip to content

Conversation

v1v
Copy link
Member

@v1v v1v commented Feb 4, 2022

What

Add debug traces.
Fix issue in the CI when using jq -r '.Version' <file> which fails with

'parse error: Invalid numeric literal at line 1, column 5'

Test

AWS_ACCESS_KEY_ID=\
AWS_SECRET_ACCESS_KEY=\
AWS_DEFAULT_REGION=us-west-2 \                
ELASTIC_LAYER_NAME=v1v-aws-lambda-test \            
make publish-in-all-aws-regions
publish 'v1v-aws-lambda-test-x86_64' in af-south-1
[debug] v1v-aws-lambda-test-x86_64 with version: 19
publish 'v1v-aws-lambda-test-x86_64' in eu-north-1
[debug] v1v-aws-lambda-test-x86_64 with version: 19
...

Further details

I cannot reproduce the error locally when parsing the json file with jq

[2022-02-04T12:27:07.386Z] publish 'elastic-apm-extension-ver0-0-3-arm64' in af-south-1
[2022-02-04T12:27:14.485Z] make[1]: Entering directory '/var/lib/jenkins/workspace/ibrary_apm-aws-lambda-mbp_v0.0.3/src/github.com/elastic/apm-aws-lambda/apm-lambda-extension'
[2022-02-04T12:27:14.485Z] parse error: Invalid numeric literal at line 1, column 5
[2022-02-04T12:27:15.257Z] 
[2022-02-04T12:27:15.257Z] usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
[2022-02-04T12:27:15.257Z] To see help text, you can run:
[2022-02-04T12:27:15.257Z] 
[2022-02-04T12:27:15.257Z]   aws help
[2022-02-04T12:27:15.257Z]   aws <command> help
[2022-02-04T12:27:15.257Z]   aws <command> <subcommand> help
[2022-02-04T12:27:15.257Z] 
[2022-02-04T12:27:15.257Z] aws: error: argument --version-number: expected one argument

@github-actions github-actions bot added the aws-λ-extension AWS Lambda Extension label Feb 4, 2022
@v1v v1v requested a review from a team February 4, 2022 12:54
@ghost
Copy link

ghost commented Feb 4, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-02-04T18:53:40.302+0000

  • Duration: 9 min 49 sec

Test stats 🧪

Test Results
Failed 0
Passed 84
Skipped 6
Total 90

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

--output json \
add-layer-version-permission \
--layer-name "$(ELASTIC_LAYER_NAME)" \
--layer-name "$(ELASTIC_LAYER_NAME)-$(ARCHITECTURE)" \
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Required fix

@v1v v1v changed the title ci: add debug traces for the publishing fix layer-name when granting public access and get ARN version Feb 4, 2022
@v1v v1v requested a review from estolfo February 7, 2022 13:39
@v1v v1v self-assigned this Feb 7, 2022
@v1v v1v added the Team:Automation Label for the Observability productivity team label Feb 8, 2022
@v1v v1v merged commit b010fd9 into elastic:main Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

aws-λ-extension AWS Lambda Extension Team:Automation Label for the Observability productivity team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants