Closed
Description
Summary
We've de-duplicated most of the workflow logic to build or rebuild user guide and API docs. This could be made reusable with the new workflow_call as we have with PR Export and Layer deployment: https://github.com/awslabs/aws-lambda-powertools-python/blob/develop/.github/workflows/reusable_export_pr_details.yml
Docs logic:
- https://github.com/awslabs/aws-lambda-powertools-python/blob/a320dddf495b0f83f9bf074075aa0f4205859b69/.github/workflows/publish.yml#L120
- https://github.com/awslabs/aws-lambda-powertools-python/blob/develop/.github/workflows/python_docs.yml
- https://github.com/awslabs/aws-lambda-powertools-python/blob/develop/.github/workflows/rebuild_latest_docs.yml
Why is this needed?
Make it easier to reuse across workflows, less error-prone, and more easily control concurrency since docs cannot be published more than once due to gh-pages push.
Which area does this relate to?
Automation
Solution
No response
Acknowledgment
- This request meets Lambda Powertools Tenets
- Should this be considered in other Lambda Powertools languages? i.e. Java, TypeScript