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

chore: remove deprecated runners_scale_up_Lambda_memory_size as it breaks CDKTF #4276

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

stefanrusu-loctax
Copy link

Hi. Thanks for this module.

I come from a CDKTF shop. CDKTF basically has a code generator based on the HCL code which generates the appropriate objects and types.

TypeScript uses camel case as default convention for symbols so that code generator produces invalid code as both the current runners_scale_up_lambda_memory_size and the legacy runners_scale_up_Lambda_memory_size are converted to the same camel cased string and the TypeScript compiler rejects that code when imported as it contains duplicate symbols.

Removing this deprecated variable enables the CDKTF users who run into this problem to successfully use this module.

This is a breaking change but I don't know for how long you do keep deprecated vars.

@stefanrusu-loctax stefanrusu-loctax changed the title Remove deprecated runners_scale_up_Lambda_memory_size as it breaks CDKTF chore: remove deprecated runners_scale_up_Lambda_memory_size as it breaks CDKTF Nov 20, 2024
@@ -21,14 +21,6 @@ variable "enable_event_rule_binaries_syncer" {
}
}


# tflint-ignore: terraform_naming_convention
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should remove as part of breaking release. I am planning one soon to remove all deprecated vars. And remove the fifo queues as well.

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

Successfully merging this pull request may close these issues.

2 participants