Cost-Related Misconfigurations Findings

Hi there! 👋

I’m a master’s student researching **cost considerations in cloud infrastructure**. As part of this project, we ran a static analysis tool (linter) on your repository to identify cost-related misconfigurations.

We found **1 potential issue** across **1 file**, which might **significantly affect the cloud costs** of your project.

Are you interested in the **linter results**? Reply here. We’ll send **the report along with a short follow-up survey** (~5 min) to evaluate our tool and better understand cost considerations in open-source projects for our research. All data will be treated confidentially.

If you’re curious about our work, we are investigating how developers approach cost in cloud infrastructure, specifically Terraform and AWS CloudFormation. Our goal is to identify **patterns and anti-patterns** to help developers make **more cost-aware infrastructure decisions**. You can check out what we’ve discovered so far here: [https://search-rug.github.io/iac-cost-patterns/](https://search-rug.github.io/iac-cost-patterns/). If you have any questions or would like to discuss our research, don’t hesitate to reach out!

Thank you for your time and support! 🤗

Allia Neamt, MSc Student (Computing Science)
Faculty of Science and Engineering
Rijksuniversiteit, Groningen

Esta es una invitación a investigar, no un issue de código accionable. Empieza revisando la página de investigación sobre patrones de costes enlazada y solicita el informe del linter si el proyecto quiere investigar el hallazgo declarado; no se proporciona ningún archivo, hallazgo ni cambio de código solicitado, por lo que la finalización no está definida.

Escrito por el modelo de indexación a partir del texto del issue.