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

cpu_core_count and cpu_threads_per_core attributes deprecation in favor of the cpu_options block #332

Closed
1 task done
schniber opened this issue May 6, 2023 · 2 comments · Fixed by #334
Closed
1 task done

Comments

@schniber
Copy link
Contributor

schniber commented May 6, 2023

Description

Terraform AWS Provider v4.66 deprecates the use of cpu_core_count and cpu_threads_per_core attributes at the aws_instance level which displays deprecation warnings when running the examples delivered with this module.

If your request is for a new feature, please use the Feature request template.

  • ✋ I have searched the open/closed issues and my issue is not listed.

Versions

  • Module version [Required]: v5.0.0

  • Terraform version: v1.4.6

  • Provider version(s): v4.66.1

Reproduction Code [Required]

Run the complete example as per this TF module.

Steps to reproduce the behavior:

Expected behavior

Terraform plan and apply execute without deprecation warnings.

Actual behavior

│ Warning: Argument is deprecated

│ with module.ec2_complete.aws_instance.this[0],
│ on ../../main.tf line 24, in resource "aws_instance" "this":
│ 24: cpu_core_count = var.cpu_core_count

│ use 'cpu_options' argument instead

Terminal Output Screenshot(s)

Additional context

@schniber schniber changed the title cpu_core_count and cpu_threads_per_core attributes deprecation in favor of the cpu_options attribute cpu_core_count and cpu_threads_per_core attributes deprecation in favor of the cpu_options block May 6, 2023
@antonbabenko
Copy link
Member

This issue has been resolved in version 5.1.0 🎉

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants