ansible-collections / ansible-collections/amazon.cloud
memorydb integration tests are disabled
- Dominant language
- Python
- Stars
- 13
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
### Summary
memorydb integration tests has been disabled in https://github.com/ansible-collections/amazon.cloud/pull/110/files because they are missing policies right now.
A PR adding the needed policies has already been created https://github.com/mattclay/aws-terminator/pull/291
### Issue Type
Bug Report
### Component Name
memorydb integration tests
### Ansible Version
```console (paste below)
$ ansible --version
```
ansible [core 2.15.0]
### Collection Versions
```console (paste below)
$ ansible-galaxy collection list
```
-
### AWS SDK versions
```console (paste below)
$ pip show boto3 botocore
```
Name: boto3
Version: 1.25.0
---
Name: botocore
Version: 1.31.17
### Configuration
```console (paste below)
$ ansible-config dump --only-changed
```
### OS / Environment
_No response_
### Steps to Reproduce
```yaml (paste below)
```
ansible-test integration memorydb
### Expected Results
Integration tests succeeding.
### Actual Results
```console (paste below)
```
### Code of Conduct
- [X] I agree to follow the Ansible Code of Conduct
Contributor guide
Research direction
Start with the `ansible-test integration memorydb` entry point and review why the memorydb integration tests were disabled in the collection changes referenced by the issue. Check the policy work in aws-terminator PR 291, then restore the tests once those policies are available and verify that the integration run succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100