Skip to content
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

ignition_file with source but without verification = malformed hash specifier #13285

Closed
jangrewe opened this issue Apr 3, 2017 · 4 comments
Closed

Comments

@jangrewe
Copy link

jangrewe commented Apr 3, 2017

Terraform Version

0.9.2

Affected Resource(s)

  • ignition_file

Terraform Configuration Files

data "ignition_file" "kubectl" {
    filesystem = "root"
    path = "/opt/bin/kubectl"
    mode = "0755"
    source {
        source = "https://storage.googleapis.com/kubernetes-release/release/v${var.k8s_version}/bin/linux/amd64/kubectl"
    }
}

Expected Behavior

The file gets downloaded, not verified, and written to the specified path.

Actual Behavior

Error refreshing state: 1 error(s) occurred:

* module.kubernetes.data.ignition_file.kubectl: 1 error(s) occurred:

* module.kubernetes.data.ignition_file.kubectl: data.ignition_file.kubectl: malformed hash specifier

Steps to Reproduce

  1. terraform plan

Important Factoids

The docs specify that verification is optional.

@jangrewe
Copy link
Author

jangrewe commented Apr 3, 2017

Probably a job for @mcuadros ;-)

@mcuadros
Copy link
Contributor

From the documentation:

When using http, it is advisable to use the verification option to ensure the contents haven’t been modified.

Actually is mandatory, I will update the documentation.

@maikzumstrull
Copy link

It's not mandatory in Ignition or Container Linux Config Transpiler, and arguably not really necessary when downloading over https (not plain http).

@ghost
Copy link

ghost commented Apr 9, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants