Skip to content
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.

Unexpected Argument Filesystem Issue #71

Open
gyalowitzdtlr opened this issue Nov 24, 2020 · 7 comments
Open

Unexpected Argument Filesystem Issue #71

gyalowitzdtlr opened this issue Nov 24, 2020 · 7 comments

Comments

@gyalowitzdtlr
Copy link

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
image

Affected Resource(s)

Please list the resources as a list, for example:

Ignition
Vsphere

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

image

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

What should have happened?
Ignition configs generate

Actual Behavior

What actually happened?
image

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform plan -out

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?
This was working without issue until I updated to the most recent ignition.

References

Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

  • GH-1234
@gyalowitzdtlr
Copy link
Author

From what I can see filesystem is part of these modules. Basically each data source is now showing as an error. Apologies up front if I am missing something simple. As always, thanks in advance for your time.

@gyalowitzdtlr gyalowitzdtlr changed the title Unexpected Arguement Filesystem Issue Unexpected Argument Filesystem Issue Nov 24, 2020
@bgilbert
Copy link

You're using the community-terraform-providers fork, not this project. That fork supports Ignition spec v3.x, not v2.x, and spec v3 removes the filesystem field.

@gyalowitzdtlr
Copy link
Author

Confusing, thank you. So using the ignition documentation, I should be able to fix my module conforming to 3.x even though none of it is reflected in the Terraform documentation?

@bgilbert
Copy link

Yes. The correct repo depends on what Linux distribution you're using though. If you're on Fedora CoreOS, you'll need the fork and spec 3.x. If you're using Flatcar Container Linux, you'll need to stay on this repo and spec 2.x.

@gyalowitzdtlr
Copy link
Author

So I would have to build this repo locally then or is it still possible to pull this through terraform?

@bgilbert
Copy link

I'm not sure; I'm not actually a Terraform user.

@gyalowitzdtlr
Copy link
Author

Thank you, I appreciate your help on this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants