Fix Elasticsearch domain instance type enum#4566
Closed
0xTaoZ wants to merge 1 commit into
Closed
Conversation
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Fixes the regional instance type enum used by
AWS::Elasticsearch::Domainso the legacy Elasticsearch resource accepts.elasticsearchinstance type names instead of OpenSearch.searchnames.Why
AWS::Elasticsearch::Domainstill uses legacy Elasticsearch instance type names such asm6g.large.elasticsearch. The enum for E3652 was populated with.searchvalues, which causes valid legacy templates to fail linting.Fixes #4565.
Details
This updates the generated enum data for the legacy Elasticsearch resource while leaving the OpenSearch resource enum separate. I also added a good fixture covering the false-positive case from #4565.
If maintainers prefer this to be fixed in the pricing/spec update path instead of committing the generated enum directly, I am happy to adjust the PR.
Testing
git diff --checkm6g.large.elasticsearchis present in theus-east-1enum andm6g.large.searchis no longer present for the legacy Elasticsearch enumNote: full local
cfn-lintexecution could not complete in my environment because enhanced schema download failed with a local SSL certificate verification error.