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

[PR #1115/f2ad6375 backport][stable-2] execute_lambda - fix check mode and update RETURN docs #1135

Conversation

patchback[bot]
Copy link

@patchback patchback bot commented May 7, 2022

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?

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)
@ansibullbot
Copy link

@ansibullbot ansibullbot added bug This issue/PR relates to a bug community_review integration tests/integration module module needs_triage new_contributor Help guide this first time contributor plugins plugin (any type) tests tests labels May 7, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 5m 07s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 08s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 13s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 54s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 58s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 12m 42s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 44s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 06s
✔️ ansible-test-splitter SUCCESS in 3m 45s
integration-community.aws-1 FAILURE in 7m 26s
⚠️ integration-community.aws-2 SKIPPED
⚠️ 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

@alinabuzachis
Copy link
Contributor

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 4m 20s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 28s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 24s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 40s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 55s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 9m 34s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 11s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 5m 58s
✔️ ansible-test-splitter SUCCESS in 3m 01s
integration-community.aws-1 FAILURE in 6m 41s
⚠️ integration-community.aws-2 SKIPPED
⚠️ 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

@markuman
Copy link
Member

markuman commented May 9, 2022

The runtime parameter of nodejs10.x is no longer supported for creating or updating AWS Lambda functions. We recommend you use the new runtime (nodejs14.x) while creating or updating functions.

same here

@markuman
Copy link
Member

markuman commented May 9, 2022

required #1108, but because it includes a new parameter, it is not backported to stable-2

@jatorcasso
Copy link
Contributor

requires #1141

@jatorcasso
Copy link
Contributor

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 5m 00s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 22s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 19s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 11s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 00s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 16s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 15s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 5m 33s
✔️ ansible-test-splitter SUCCESS in 2m 43s
✔️ integration-community.aws-1 SUCCESS in 9m 01s
⚠️ integration-community.aws-2 SKIPPED
⚠️ 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

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

Build succeeded (gate pipeline).

ansible-galaxy-importer FAILURE in 4m 43s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 50s
✔️ ansible-test-sanity-docker-devel SUCCESS in 9m 59s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 18s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 14m 14s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 06s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 35s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 14s
✔️ ansible-test-splitter SUCCESS in 2m 57s
✔️ integration-community.aws-1 SUCCESS in 8m 42s
⚠️ integration-community.aws-2 SKIPPED
⚠️ 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 softwarefactory-project-zuul bot merged commit 0152bb0 into stable-2 May 10, 2022
@softwarefactory-project-zuul softwarefactory-project-zuul bot deleted the patchback/backports/stable-2/f2ad6375ad5ff0d07158f7b8248968b1d5e08966/pr-1115 branch May 10, 2022 05:17
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
…collections#1135)

Remove deprecated CloudRetry.backoff (and AWSRetry.backoff)

SUMMARY
Originally slated for removal in 4.0.0 and backed off to 6.0.0 in ansible-collections#951.  Now that we've branched stable-5 we can remove the deprecated decorator
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
plugins/module_utils/cloud.py
ADDITIONAL INFORMATION
fixes: ansible-collections#1110

Reviewed-by: Alina Buzachis <None>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue/PR relates to a bug community_review integration tests/integration mergeit Merge the PR (SoftwareFactory) module module new_contributor Help guide this first time contributor plugins plugin (any type) tests tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants