-
Notifications
You must be signed in to change notification settings - Fork 397
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
elb_target_group: Add support for protocol_version parameter #1496
elb_target_group: Add support for protocol_version parameter #1496
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
... @sharvarikhedkar thank you for the PR. |
changelogs/fragments/1496-elb_target_group-add-protocol_version-support.yml
Outdated
Show resolved
Hide resolved
- name: Create a target group with protocol_version 'GRPC' (idempotence) | ||
community.aws.elb_target_group: | ||
name: "{{ elb_target_group_name }}" | ||
protocol: http | ||
port: 80 | ||
vpc_id: "{{ vpc.vpc.id }}" | ||
protocol_version: GRPC | ||
state: present | ||
register: create_result | ||
|
||
- assert: | ||
that: | ||
- create_result is not changed | ||
- create_result is not failed | ||
- create_result.protocol_version == "GRPC" | ||
- create_result.protocol == "HTTP" | ||
- create_result.port == 80 |
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.
@sharvarikhedkar can you also please a third test that verify that a change of the protocol_version
works properly?
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.
...otherwise LGTM
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.
Hi @markuman, I tried testing the code for updating the target group with different protocol_versions but looking at the boto3 documentation and trying to modify protocol_version
through AWS console, it seems like the update operation for protocol_version
parameter is not supported yet, any insights on this?
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.
Oh, I didn't know that. Maybe that should be mentioned than in the module documentation @sharvarikhedkar
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.
Added.
recheck |
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #1577 🤖 @patchback |
elb_target_group: Add support for protocol_version parameter SUMMARY Added support for protocol_version param in elb_target_group. Fixes 1422. ISSUE TYPE Feature Pull Request COMPONENT NAME elb_target_group Reviewed-by: Gonéri Le Bouder <[email protected]> Reviewed-by: Sharvari Khedkar <None> Reviewed-by: Markus Bergholz <[email protected]> (cherry picked from commit 02bbc54)
…1577) [PR #1496/02bbc544 backport][stable-5] elb_target_group: Add support for protocol_version parameter This is a backport of PR #1496 as merged into main (02bbc54). SUMMARY Added support for protocol_version param in elb_target_group. Fixes 1422. ISSUE TYPE Feature Pull Request COMPONENT NAME elb_target_group Reviewed-by: Markus Bergholz <[email protected]>
SUMMARY
Added support for
protocol_version
param inelb_target_group
.Fixes 1422.
ISSUE TYPE
COMPONENT NAME
elb_target_group