Skip to content

Support ignoring changes to specific environment variables #692

@myrkytyn

Description

@myrkytyn

Is your request related to a new offering from AWS?

My request is to enhance the functionality and flexibility of the module with existing AWS functionality.

Is your request related to a problem? Please describe.

My team uses the Lambda module to manage AWS Lambda functions. Some environment variables are set using the AWS SDK (e.g., secrets injected during deployment by CI/CD). In the Terraform configuration, I provide dummy values for these environment variables.

However, this results in Terraform drift, and during the next terraform apply, the real values are overwritten by these dummy placeholders.

Describe the solution you'd like.

I would like the module to support an option to ignore changes to specific environment variables. This would leverage Terraform’s lifecycle.ignore_changes feature.

Example:

environment_variables = {
  ENV1 = "dummy value 1"
  ENV2 = "dummy value 2"
  ENV3 = "real value"
}

ignore_environment_variables = ["ENV1", "ENV2"]

Describe alternatives you've considered.

Before submitting this feature request, I considered and tried two approaches:

  • Managing Lambda functions directly using the aws_lambda_function resource to enable ignore_changes.
  • Downloading the module and modifying it locally to include ignore_changes.

Additional context

I'm opening this feature request to get feedback from module maintainers and the community. I'm also reviewing the contributing guide and module structure to explore a possible implementation path and contribute the feature myself, if acceptable.

Let me know if this idea aligns with the module's goals. Any feedback or suggestions are appreciated!

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