Super cool ! Can we test this ?
yes directly by signing up on our app https://app.anyshift.io/sign-in
Show HN: Anyshift.io – Terraform "Superplan"
21–30 of 47 posts
Re: Show HN: Anyshift.io – Terraform "Superplan"
#22Earlier quoted context omitted.
Ok focusing on context makes sense but I’d challenge the idea that LLMs inherently fail without it. Some teams have used fine-tuned models or hybrid workflows with partial context to generate useful IaC snippets
Agreed 100%. LLMs are doing solid job at generating IaC but in a context where the person who use them knows what he/she's doing. In our case, remediaiton means an extra level of trust, where your infra is already super sensitive.
we have used some tools to generate terraform code based on our unmanaged cloud resource for instance and it worked well..
Re: Show HN: Anyshift.io – Terraform "Superplan"
#23Earlier quoted context omitted.
Thanks for the feedback! We already use AI in the PR to explain whats happening and the best practices to adopt. As for the code remediation part: most LLMs fail to generate the right IaC code thats adapted to your infra because they miss its general context (config, dependencies..). We are building first the deterministic part (the context) and once we have the context our plan is to add the fix/recommendation in th…
How will you be checkiing the quality of the AI recommendations in the your PR. Do you think that using different model ( chatgpt, claude,gemin, qwen) to challenge the recommendation made by another AI could help ?
About having differents models challenging each other, I haven’t seen anything useful yet but I understand where you are going. Might be a future direction
Re: Show HN: Anyshift.io – Terraform "Superplan"
#24[dead]
Re: Show HN: Anyshift.io – Terraform "Superplan"
#25This is such a cool idea! I’ve run into the pain of navigating Terraform dependencies before, and your graph-based approach feels really promising.
I’m especially intrigued by the "time machine", how does it manage historical state changes in larger environments without requiring you to start a side-business in cloud storage? ^^
Excited to give this a spin. Amazing work!
Re: Show HN: Anyshift.io – Terraform "Superplan"
#26Earlier quoted context omitted.
Agreed 100%. LLMs are doing solid job at generating IaC but in a context where the person who use them knows what he/she's doing. In our case, remediaiton means an extra level of trust, where your infra is already super sensitive.
we have used some tools to generate terraform code based on our unmanaged cloud resource for instance and it worked well..
The tools we are aware of will create a 1-to-1 mapping to some code, but very often with hardcoded values because they lack the full context of your infrastructure. This can lead to potential incidents in the future (broken dependencies / visibility). This is at least the way we are approaching it, and why we want to build this "deterministic" part first and then use it as context to the LLMs.
Re: Show HN: Anyshift.io – Terraform "Superplan"
#27Terraform plan on steroids? Love it Do you have plans to interlink with other observability platforms?
we are thinking to add live monitoring data to it such as datadog or prometheus. What do you use ?
Re: Show HN: Anyshift.io – Terraform "Superplan"
#28This is such a cool idea! I’ve run into the pain of navigating Terraform dependencies before, and your graph-based approach feels really promising. I’m especially intrigued by the "time machine", how does it manage historical state changes in larger environments without requiring you to start a side-business in cloud storage? ^^ Excited to give this a spin. Amazing work!
This mean searching through time and changes. Imagine prod is on fire and api returns 500. Often you need to check through logs, git, cloud consoles, kub configs etc... with the time machine, Anyshift will directly return the list of 5 changes that occured during the week, including the autoscaler and who did the change
Re: Show HN: Anyshift.io – Terraform "Superplan"
#29[dead]
Re: Show HN: Anyshift.io – Terraform "Superplan"
#30Earlier quoted context omitted.
In our Pull Request bot, we provide more information with a clear sumup of whats gonna be impacted. One of our next feature is to configure what type of information is more critical to you: by type of resources, owner (git blame) and tags. Do you have one that you would prefer in particular ?
I guess by type of resources but also env would be interesting. I don't care on most of the impact of my dev end tbh.
super interesting thanks! for having config combined