[Bug]: aws-deployment-framework-base pipeline fails

[Wildpipe]

[Bug]: aws-deployment-framework-base pipeline fails

[Wildpipe]

I believe this issue is related to a broken version of PyYAML: yaml/pyyaml#724

[sbkok]

Unfortunately I cannot reproduce your issue with v3.2.0.
@Wildpipe can you please elaborate on the version you are running?

Specifically, I see your logs reference Python 3.11, which is a version that is not supported by CDK v1 that is used by ADF v3.2.0. Might you be running any patches that are merged in our main branch today?
It looks like you are running our CDK v2 patch at least. And what CodeBuild image is used specifically?

[Wildpipe]

Yes, we are running the CDK v2 patch.
For CodeBuild image we are running aws/codebuild/standard:7.0

I managed to "fix" the problem by implementing the following changes:

Comment out this line

aws-deployment-framework/src/lambda_codebase/initial_commit/bootstrap_repository/adf-build/requirements.txt

Line 12 in e348ed1

pyyaml~=5.4

Append the following lines to

aws-deployment-framework/src/lambda_codebase/initial_commit/bootstrap_repository/adf-bootstrap/deployment/global.yml

Line 691 in e348ed1

- aws s3 cp s3://$SHARED_MODULES_BUCKET/adf-build/ ./adf-build/ --recursive --quiet

- pip install wheel
- pip install --no-build-isolation "Cython<3" "pyyaml==5.4.1"

Append the following lines to https://github.com/awslabs/aws-deployment-framework/blob/e348ed1a4144d26d0fd7ed6866c8a663f9111141/src/lambda_codebase/initial_commit/bootstrap_repository/adf-bootstrap/deployment/pipeline_management.yml#L667C35-L667C56

- pip install wheel
- pip install --no-build-isolation "Cython<3" "pyyaml==5.4.1"

Sorry, I wasn't aware we had diverged from main branch in terms of codebuild image.

[Wildpipe]

Looking at the cdkv2 patch that seems to be what introduced the standard:7.0 change

[sbkok]

Okay, phew. I am about to perform an upgrade of ADF v3.2.0 at another large installation.
I was worried this would impact v3.2.0 upgrades too, blocking our ability to upgrade.
I will get a PR in the main branch to fix this issue. Thanks for sharing that workaround.