Skip to content
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

Feature |  Add a Tag to Resources Indicating the Layer #518

Open
exequielrafaela opened this issue Jun 20, 2023 · 0 comments
Open

Feature |  Add a Tag to Resources Indicating the Layer #518

exequielrafaela opened this issue Jun 20, 2023 · 0 comments

Comments

@exequielrafaela
Copy link
Member

Describe the Feature

Expected Behavior

Once implemented, each resource should have a tag indicating the layer. This should aid in tracking the code that created the implementation.

Use Case

This feature is valuable for improving code traceability and documentation. It will provide a direct link between resources and the layer that created them, making it easier to understand and manage the codebase.

Describe Ideal Solution

The ideal solution would involve adding a tag to each resource during its creation, indicating the layer. The tag should be easily visible and accessible for reference. Consideration should be given to whether the tag can be obtained through a function or similar method to avoid the hardcoded example below.

locals {
  tags = {
    Terraform   = "true"
    Environment = var.environment
    Layer = "base-dns/binbash.co"
  }
}

Alternatives Considered

An alternative could be to continue without these tags, relying on developers to remember or find the relevant layer for each resource. However, this could lead to inefficiencies and potential errors.

Additional Context

This feature request arose from a discussion about improving code traceability and documentation. The addition of a layer tag to each resource was suggested as a potential solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant