-
Notifications
You must be signed in to change notification settings - Fork 982
fast/extras/0-cicd-github creates corrupted PNG (base 64 encoded content) #2503
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
Comments
I can't see how https://registry.terraform.io/providers/integrations/github/latest/docs/resources/repository_file actually supports uploading a binary file (there's no flag to let it know that the content is base64 encoded). This commit totally doesn't work (for me) |
My guess is that the actual error message comes from around here. But due how the code looks as of now you should not get this exact message. This suggests that you use v5.43.0 or earlier of github provider. Is this the case? Can you try with newer version? |
My last attempt was with opentofu:
PS: it "works fine" if I comment out the Will reinstall terraform, and see which version it installed. Sec. |
Even with latest terraform, and running
|
Given there seems to be little to fix on our side, can we close this issue? |
Maybe it would be worth it to mention this in the stage README, what do you think? |
Yes, documenting "this process will corrupt any binary files, including PNG". In the alternative, maybe a non-terraform solution would work better? |
Describe the bug
Applying fast/extras/0-cicd-github creates corrupted PNG output and ultimately fails with error.
Environment
Also tried with opentofu (same result)
To Reproduce
Create a tfvars with any repo:
Execute: terraform init + apply
Look at PNG in the output - they are base64 encoded text, not the original binary content.
Expected behavior
Files in the new repos to be intact, and mostly identical to the original.
Result
Terraform output and/or error messages
Additional context
Add any other context about the problem here
The text was updated successfully, but these errors were encountered: