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

Add missing elements option to type: list that did not specify #1116

Conversation

jatorcasso
Copy link
Contributor

SUMMARY

Fixes #1114

ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME
  • cloudfront_distribution
  • ecs_taskdefinition
  • elb_application_lb
  • rds_option_group

@github-actions
Copy link

github-actions bot commented May 4, 2022

Docs Build 📝

Thank you for contribution!✨

This PR has been merged and your docs changes will be incorporated when they are next published.

@ansibullbot
Copy link

@jatorcasso jatorcasso changed the title Add missing elements option to type: lists that did not specify Add missing elements option to type: list that did not specify May 4, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 08s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 56s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 37s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 23s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 47s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 18s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 11m 42s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 43s
✔️ ansible-test-splitter SUCCESS in 3m 35s
✔️ integration-community.aws-1 SUCCESS in 7m 19s
✔️ integration-community.aws-2 SUCCESS in 6m 44s
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 05s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 16s
✔️ ansible-test-sanity-docker-devel SUCCESS in 11m 08s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 26s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 32s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 9m 33s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 11m 39s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 29s
✔️ ansible-test-splitter SUCCESS in 3m 03s
✔️ integration-community.aws-1 SUCCESS in 13m 24s
✔️ integration-community.aws-2 SUCCESS in 7m 33s
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@jatorcasso
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 48s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 01s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 28s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 59s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 38s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 12m 06s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 50s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 33s
✔️ ansible-test-splitter SUCCESS in 3m 10s
✔️ integration-community.aws-1 SUCCESS in 7m 36s
✔️ integration-community.aws-2 SUCCESS in 8m 37s
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@jatorcasso jatorcasso closed this May 5, 2022
@jatorcasso jatorcasso reopened this May 5, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 54s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 56s
✔️ ansible-test-sanity-docker-devel SUCCESS in 11m 13s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 46s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 02s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 11m 47s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 37s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 29s
✔️ ansible-test-splitter SUCCESS in 2m 56s
✔️ integration-community.aws-1 SUCCESS in 9m 00s
✔️ integration-community.aws-2 SUCCESS in 6m 56s
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

Copy link
Collaborator

@jillr jillr left a comment

Choose a reason for hiding this comment

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

Thanks @jatorcasso!

@jillr jillr added the mergeit Merge the PR (SoftwareFactory) label May 5, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded (gate pipeline).

ansible-galaxy-importer FAILURE in 4m 15s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 48s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 05s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 36s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 13m 17s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 12s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 54s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 7m 01s
✔️ ansible-test-splitter SUCCESS in 3m 11s
✔️ integration-community.aws-1 SUCCESS in 9m 14s
✔️ integration-community.aws-2 SUCCESS in 8m 14s
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul
Copy link
Contributor

Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry.

jatorcasso added a commit to jatorcasso/community.aws that referenced this pull request May 6, 2022
…ible-collections#1116)

Add missing `elements` option to type: list that did not specify

SUMMARY
Fixes ansible-collections#1114
ISSUE TYPE

Docs Pull Request

COMPONENT NAME

cloudfront_distribution
ecs_taskdefinition
elb_application_lb
rds_option_group

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Jill R <None>
(cherry picked from commit c1d47dd)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 6, 2022
lambda - fix check mode on creation

Depends-On: #1116
SUMMARY


When adding integration tests for check mode runs, creating a lambda function failed on check mode with the message "Unable to get function information after creating".


Added parameter kms_key_arn - testing in integration tests appears difficult as I think we'd need to create an IAM policy to allow for adding kms_key, which would render these tests as unsupported.


Added extra waiter for function_update in execute_lambda to resolve occasional integration test failure.


Fixes #1111
ISSUE TYPE

Feature Pull Request
Bugfix Pull Request

COMPONENT NAME
lambda

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>
patchback bot pushed a commit that referenced this pull request May 6, 2022
lambda - fix check mode on creation

Depends-On: #1116
SUMMARY

When adding integration tests for check mode runs, creating a lambda function failed on check mode with the message "Unable to get function information after creating".

Added parameter kms_key_arn - testing in integration tests appears difficult as I think we'd need to create an IAM policy to allow for adding kms_key, which would render these tests as unsupported.

Added extra waiter for function_update in execute_lambda to resolve occasional integration test failure.

Fixes #1111
ISSUE TYPE

Feature Pull Request
Bugfix Pull Request

COMPONENT NAME
lambda

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit 0bde6bb)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 6, 2022
[PR #1108/0bde6bbd backport][stable-3] lambda - fix check mode on creation

This is a backport of PR #1108 as merged into main (0bde6bb).
Depends-On: #1116
SUMMARY


When adding integration tests for check mode runs, creating a lambda function failed on check mode with the message "Unable to get function information after creating".


Added parameter kms_key_arn - testing in integration tests appears difficult as I think we'd need to create an IAM policy to allow for adding kms_key, which would render these tests as unsupported.


Added extra waiter for function_update in execute_lambda to resolve occasional integration test failure.


Fixes #1111
ISSUE TYPE

Feature Pull Request
Bugfix Pull Request

COMPONENT NAME
lambda

Reviewed-by: Alina Buzachis <None>
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 7, 2022
execute_lambda - fix check mode and update RETURN docs

Depends-On: #1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Sloane Hertel <None>
Reviewed-by: Markus Bergholz <[email protected]>
patchback bot pushed a commit that referenced this pull request May 7, 2022
execute_lambda - fix check mode and update RETURN docs

Depends-On: #1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Sloane Hertel <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit f2ad637)
patchback bot pushed a commit that referenced this pull request May 7, 2022
execute_lambda - fix check mode and update RETURN docs

Depends-On: #1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Sloane Hertel <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit f2ad637)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 9, 2022
rds_instance - add deletion_protection param

Depends-On: #1116
SUMMARY
Fixes #922
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>
patchback bot pushed a commit that referenced this pull request May 9, 2022
rds_instance - add deletion_protection param

Depends-On: #1116
SUMMARY
Fixes #922
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit 77cb097)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 9, 2022
[PR #1115/f2ad6375 backport][stable-3] execute_lambda - fix check mode and update RETURN docs

This is a backport of PR #1115 as merged into main (f2ad637).
Depends-On: #1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Alina Buzachis <None>
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 9, 2022
[PR #1105/77cb0974 backport][stable-3] rds_instance - add deletion_protection param

This is a backport of PR #1105 as merged into main (77cb097).
Depends-On: #1116
SUMMARY
Fixes #922
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance

Reviewed-by: Alina Buzachis <None>
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 10, 2022
[PR #1115/f2ad6375 backport][stable-2] execute_lambda - fix check mode and update RETURN docs

This is a backport of PR #1115 as merged into main (f2ad637).
Depends-On: #1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Joseph Torcasso <None>
@tremble tremble mentioned this pull request May 17, 2022
1 task
@tremble tremble linked an issue May 17, 2022 that may be closed by this pull request
1 task
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 25, 2022
rds_instance_snapshot - add copy snapshot functionality

Depends-On: ansible-collections/amazon.aws#776
Depends-On: #1116
SUMMARY

Add support for copying a snapshot
Fixes #210
Don't require db_instance_identifier on state = present (only required for creation)

ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance_snapshot

Reviewed-by: Markus Bergholz <[email protected]>
Reviewed-by: Joseph Torcasso <None>
Reviewed-by: Alina Buzachis <None>
patchback bot pushed a commit that referenced this pull request May 25, 2022
rds_instance_snapshot - add copy snapshot functionality

Depends-On: ansible-collections/amazon.aws#776
Depends-On: #1116
SUMMARY

Add support for copying a snapshot
Fixes #210
Don't require db_instance_identifier on state = present (only required for creation)

ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance_snapshot

Reviewed-by: Markus Bergholz <[email protected]>
Reviewed-by: Joseph Torcasso <None>
Reviewed-by: Alina Buzachis <None>
(cherry picked from commit d04ab42)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 26, 2022
[PR #1078/d04ab427 backport][stable-3] rds_instance_snapshot - add copy snapshot functionality

This is a backport of PR #1078 as merged into main (d04ab42).
Depends-On: ansible-collections/amazon.aws#776
Depends-On: #1116
SUMMARY

Add support for copying a snapshot
Fixes #210
Don't require db_instance_identifier on state = present (only required for creation)

ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance_snapshot

Reviewed-by: Markus Bergholz <[email protected]>
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
lambda - fix check mode on creation

Depends-On: ansible-collections#1116
SUMMARY

When adding integration tests for check mode runs, creating a lambda function failed on check mode with the message "Unable to get function information after creating".

Added parameter kms_key_arn - testing in integration tests appears difficult as I think we'd need to create an IAM policy to allow for adding kms_key, which would render these tests as unsupported.

Added extra waiter for function_update in execute_lambda to resolve occasional integration test failure.

Fixes ansible-collections#1111
ISSUE TYPE

Feature Pull Request
Bugfix Pull Request

COMPONENT NAME
lambda

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections@0bde6bb
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
…ctions#1115)

execute_lambda - fix check mode and update RETURN docs

Depends-On: ansible-collections#1116
SUMMARY

check_mode fix
update RETURN docs to match what is actually being returned
require one of name, function_arn

ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
execute_lambda
ADDITIONAL INFORMATION
I noticed some modules in community.aws will return data directly, and others will return data nested in a dict.
Example: let iam_group be the module, retrieving a key called group_arn, and registering the response as response. Some modules you would need to query result.iam_group.group_arn, meanwhile in others, you can result.group_arn (where iam_group is assumed, since its the name of the module). Do we have a preference for either method? Should we come to some sort of collection-wide consensus on which to use moving forward?

Reviewed-by: Sloane Hertel <None>
Reviewed-by: Markus Bergholz <[email protected]>

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections@f2ad637
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
rds_instance - add deletion_protection param

Depends-On: ansible-collections#1116
SUMMARY
Fixes ansible-collections#922
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Markus Bergholz <[email protected]>

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections@77cb097
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
…ections#1078)

rds_instance_snapshot - add copy snapshot functionality

Depends-On: ansible-collections/amazon.aws#776
Depends-On: ansible-collections#1116
SUMMARY

Add support for copying a snapshot
Fixes ansible-collections#210
Don't require db_instance_identifier on state = present (only required for creation)

ISSUE TYPE

Feature Pull Request

COMPONENT NAME
rds_instance_snapshot

Reviewed-by: Markus Bergholz <[email protected]>
Reviewed-by: Joseph Torcasso <None>
Reviewed-by: Alina Buzachis <None>

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections@d04ab42
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
…ible-collections#1116)

Add missing `elements` option to type: list that did not specify

SUMMARY
Fixes ansible-collections#1114
ISSUE TYPE

Docs Pull Request

COMPONENT NAME

cloudfront_distribution
ecs_taskdefinition
elb_application_lb
rds_option_group

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Jill R <None>

This commit was initially merged in https://github.com/ansible-collections/community.aws
See: ansible-collections@c1d47dd
abikouo added a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
…1095)

new modules: lambda_layer and lambda_layer_info

SUMMARY

The module lambda_layer allows user to publish or delete lambda layer version, while lambda_layer_info is used to list lambda layers or all versions of a specific lambda layer

ISSUE TYPE


New Module Pull Request

COMPONENT NAME

lambda_layer
lambda_layer_info
ADDITIONAL INFORMATION





Closes: ansible-collections#1116

Reviewed-by: Mark Chappell <None>
Reviewed-by: Bikouo Aubin <None>
Reviewed-by: Jill R <None>
Reviewed-by: Alina Buzachis <None>
Reviewed-by: Gonéri Le Bouder <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community_review docs mergeit Merge the PR (SoftwareFactory) module module plugins plugin (any type)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ansible-test-sanity-docker-milestone failing CI New sanity test failures (devel)
4 participants