ansible-collections / ansible-collections/amazon.cloud
How to create the contents of the config directory (modules.yaml and api_specification)
- Dominant language
- Python
- Stars
- 13
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
### Summary
I would like to understand how the contents of the `config/` directory are created - I understand that they come via CloudFormations, but I was wondering whether they are automatically generated, or whether they are human generated and then ingested at build time? I've tried rebuilding the collection using Content Builder without the `api_specification` directory, and it only created a very limited number of modules. Can more details on how this directory is created/updated be included in the documentation please?
### Issue Type
Documentation Report
### Component Name
Content Builder configuraiton
### Ansible Version
```console (paste below)
$ ansible --version
```
### Collection Versions
```console (paste below)
$ ansible-galaxy collection list
```
### Configuration
```console (paste below)
$ ansible-config dump --only-changed
```
### OS / Environment
_No response_
### Additional Information
_No response_
### Code of Conduct
- [X] I agree to follow the Ansible Code of Conduct
Contributor guide
Research direction
Start by reviewing the config/ directory, including modules.yaml and api_specification, and the existing Content Builder documentation. Trace how these contents are created or updated, then document whether they are generated or human-authored and how they affect collection rebuilding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100