Skip to content
This repository has been archived by the owner on Sep 9, 2022. It is now read-only.

output not sorted #319

Open
dancadar opened this issue Mar 31, 2017 · 4 comments
Open

output not sorted #319

dancadar opened this issue Mar 31, 2017 · 4 comments

Comments

@dancadar
Copy link

Maybe it does not really fit into "Issues", but the output of terraforming is not sorted - meaning that (at least for) security groups are not always in the same order; permissions are not always in the same order and ip_ranges/security_groups are not always in the same order inside a security group's permissions.

And it might happen with other resources as well, but i've noticed that on security_groups.

@pchaganti
Copy link

👍

@mumoshu
Copy link

mumoshu commented May 17, 2018

I encountered this too. For me, running terraform plan against the the tf file and the tfstate generated by terraforming shows a bunch of removal/addition of equivalent sg rules due to this ordering issue.

@mumoshu
Copy link

mumoshu commented May 17, 2018

@mumoshu
Copy link

mumoshu commented May 18, 2018

I can consistently reproduce my problem by running:

for i in $(seq 5); do bundle exec terraforming s3 > $i.tf && bundle exec terraforming s3 --tfstate > $i.tfstate && mkdir -p tfprojs/$i; mv $i.tf{,state} tfprojs/$i/; done

and

for i in $(seq 5); do cd tfprojects/$i; terraform init && terraform plan -state $i.tfstate; done

There are bunch of changes. I don't see a complete picture yet. At least, not only sg but also s3 resources show differences.

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

3 participants