-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(eks): Allow helm pull from non-ECR OCI repositories #25237
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
d54c871
to
8a0b1ce
Compare
8a0b1ce
to
86febbe
Compare
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
This fixes an issue that occurs when installing Helm charts from OCI repositories other than ECR (e.g.
oci://ghcr.io/grafana-operator/helm-charts/grafana-operator
).The issue occurs because
subprocess.check_output
is called withshell=True
, which only invokes the first item of the passed cmnd sequence. So instead ofhelm pull $REPO --version $VERSION --untar
, onlyhelm
is executed, which results in the following output (also observed in the Lambda logs):Output
From the
subprocess
logs:See https://docs.python.org/3/library/subprocess.html#popen-constructor
Merging the
helm
command and its arguments into the first item of thecmnd
list fixes the issue.To quickly verify the fix, this code can be added to the file:
Without the fix, running the file with Python should then result in the behaviour described above. With the fix the chart should be pulled correctly into the temporary directory.
Closes #24710
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license