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

feat: Add output for cluster TLS certificate SHA1 fingerprint and provider tags to cluster primary security group #2249

Merged

Conversation

bryantbiggs
Copy link
Member

Description

  • Add output for cluster TLS certificate SHA1 fingerprint
  • Add provider default tags to EKS created security group for tag stability
  • Update user data variable description to clarify its usage with ami_id

Motivation and Context

Breaking Changes

  • No

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

Copy link
Member

@antonbabenko antonbabenko left a comment

Choose a reason for hiding this comment

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

Minor correction and LGTM

main.tf Outdated Show resolved Hide resolved
@bryantbiggs bryantbiggs merged commit a74e980 into terraform-aws-modules:master Sep 29, 2022
@bryantbiggs bryantbiggs deleted the feat/sha1-fingerprint branch September 29, 2022 19:34
antonbabenko pushed a commit that referenced this pull request Sep 29, 2022
## [18.30.0](v18.29.1...v18.30.0) (2022-09-29)

### Features

* Add output for cluster TLS certificate SHA1 fingerprint and provider tags to cluster primary security group ([#2249](#2249)) ([a74e980](a74e980))
@antonbabenko
Copy link
Member

This PR is included in version 18.30.0 🎉

@github-actions
Copy link

github-actions bot commented Nov 8, 2022

I'm going to lock this pull request 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 related to this change, 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 Nov 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants