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

How to create the contents of the config directory (modules.yaml and api_specification) #123

Open
1 task done
jamesfreeman959 opened this issue Apr 8, 2024 · 1 comment
Labels
documentation Improvements or additions to documentation

Comments

@jamesfreeman959
Copy link

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

$ ansible --version

Collection Versions

$ ansible-galaxy collection list

Configuration

$ ansible-config dump --only-changed

OS / Environment

No response

Additional Information

No response

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@gravesm
Copy link
Member

gravesm commented Apr 22, 2024

The modules.yaml file is created by hand. The schema files in api_specification are automatically generated by the content builder when plugin:action is either generate_schema or generate_all.

@gravesm gravesm added the documentation Improvements or additions to documentation label Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants