-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Required attributes are deleted when empty #137
Comments
|
It'll take me a while to move to 0.12. There are internal changes in TF, so want to make sure everything is working as expected. |
Yes, but it doesn't apply for arrays it seem. It's trivial to add the check for
OK, I guess it's better to wait after your 0.12 rewrite, but will you accept a PR to add |
You right, removing empty array it's before AllowEmptyValue checking. |
Currently, the `ConvertTFstate` is deleting keys of type arrays which are empty, without checking the `allowEmptyValues` argument. This commit is intended to fix that. GoogleCloudPlatform#137
Currently, the `ConvertTFstate` is deleting keys of type arrays which are empty, without checking the `allowEmptyValues` argument. This commit is intended to fix that. GoogleCloudPlatform#137
While trying to add support for a new provider, running import doesn't include some required attributes for the resource in the generated TF file. This is because in the
ConvertTFstate
function of the resource, it delete keys from attributes which are empty. There is anAllowEmptyValue
argument which can be used to allow attributes with empty values, but not for those of type array (List).Instead of deleting empty attributes from HCL generation, wouldn't it be better if it was checked against the schema for the resources and only remove the attributes which don't have
Required
set totrue
?The text was updated successfully, but these errors were encountered: