Skip to content

Terraform Power - Kiro does not respect recommended files in code-style.md #19

@acwwat

Description

@acwwat

Kiro version: 0.7.34 (user setup)
OS: Windows_NT x64 10.0.22631 (Windows 11)

After installing the Terraform power, I tried using the Try power option to test it out. After specifying "AWS" as the provider, Kiro created the basic file structure as follows:

├── versions.tf              # Terraform and provider version constraints
├── provider.tf              # AWS provider configuration
├── variables.tf             # Input variables
├── main.tf                  # Main resources (S3 bucket example)
├── outputs.tf               # Output values
├── terraform.tfvars.example # Example variable values
└── .gitignore              # Git ignore patterns

What I noticed is that provider.tf is NOT the recommended file name in the power's code-style.md - it should have been providers.tf with a 's' instead. Knowing this information, I asked Kiro the following:

The terraform power steering file should have already mentioned that provider.tf should be named providers.tf. Why is it not correct with the file you generated? Are you not following the steering rules?

The response is as per the screenshot below:

Image

So Kiro referred only to the file structure and not the information in the "Recommended Files" section. If I expand the "Read power steering" section, I can see that it is only getting results from terraform-best-practices.md, not code-style.md:

Image

When I asked the following question as a follow-up:

Can you list the recommended files in the coding style guidelines in the terraform power?

It was able to recognize the information in the Required Files and Recommended Files sections in the steering file and suggests to update the generated file structure:

Image

And if I expand the "Read power steering" section, I can see that it is reading (only) from code-style.md:

Image

The expected behavior should be that Kiro should be aware of the all steering files regardless of situation and name the files appropriately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions