-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
d/aws_prefix_list: add support for managed prefix lists #14110
Closed
roberth-k
wants to merge
8
commits into
hashicorp:master
from
roberth-k:f-aws_prefix_list-data-source-managed-prefix-list
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
37c49d9
d/aws_prefix_list: fix name filter override and lack of error when ma…
roberth-k f259a03
d/aws_prefix_list: sort cidrs
roberth-k 3d2ca8e
d/aws_prefix_list: fix doc type and add example about finding a prefi…
roberth-k a35c88c
d/aws_prefix_list: error check when setting cidr_blocks
roberth-k 354559c
r/aws_prefix_list: new resource
roberth-k 49921b1
Merge branch 'f-aws_managed_prefix_list' into f-aws_prefix_list-data-…
roberth-k e46e4e4
Merge branch 'b-aws_prefix_list' into f-aws_prefix_list-data-source-m…
roberth-k ccd00bf
d/aws_prefix_list: add managed prefix list support
roberth-k File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a very forward comment here since it will dramatically change the implementation -- rather than change the API call associated with the existing data source, which can cause issues in environments that utilize restrictive IAM permissions or with AWS "compatible" APIs that may not support the new API call, the preference would be to create a separate data source so operators can choose the appropriate solution. 👍
It may be easiest to close this pull request and separately submit a pull request with just a new
aws_ec2_managed_prefix_list
data source that for now just tests AWS managed prefix lists. Once #14068 is merged, we can add any remaining functionality to the new data source.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bflad,
I hadn't considered this detail, and it makes the right course clear in retrospect. Indeed, the managed prefix list API-s require a different set of IAM actions.
Just to confirm, is
aws_ec2_managed_prefix_list
(as well asaws_ec2_managed_prefix_list_entry
in the resource PR) the preferred nomenclature?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, please, and thank you regarding the naming! We can separately discuss the merits of an
_entry
resource in the other pull request.