Limit & KeyID Feature for Keys DataSource #2538
Merged
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.
Current Behavior
The KP Terraform data source doesn't have provision to search all keys in an instance for a given key-name as an input. Moreover, there is a limitation in KP SDK which limits the number of keys to 2000 when it is not overwritten. Due to this behaviour, there are chances that the user may not be able to retrieve the required key when searching based on the key name and hence this behaviour need to be updated with the following changes so that the user has the flexibility to include all the keys to search for the required key name and also able to search based on key_id & key_alias.
Expected Behavior