gh-actions | Github action for generating Terraform module documentation | Infrastructure Automation library
kandi X-RAY | gh-actions Summary
kandi X-RAY | gh-actions Summary
A Github action for generating Terraform module documentation using terraform-docs and gomplate
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gh-actions
gh-actions Key Features
gh-actions Examples and Code Snippets
name: Generate terraform docs
on:
- pull_request
jobs:
docs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
with:
ref: ${{ github.event.pull_request.head.ref }}
- name: Render terraform docs inside the US
- name: Generate TF Docs
uses: terraform-docs/gh-actions@v0.11.0
with:
working-dir: .,example1,example3/modules/test
output-file: README.md
- name: Generate TF Docs
uses: terraform-docs/gh-actions@v0.11.0
with:
working-dir: .
output-file: README.md
Community Discussions
Trending Discussions on gh-actions
QUESTION
ANSWER
Answered 2021-Dec-07 at 17:37I might be wrong but I think you should have
DATABASE_URL: mysql://root:password@localhost:3306/db
?
QUESTION
I am trying to use tox-gh-actions to automate testing on github pushes. In order to test the implementation, I am locally using tox with setup.cfg, command I use python -m tox
but I always end up with the error:
ANSWER
Answered 2021-Sep-30 at 14:31Note that setup.cfg requires the content to be under the tox:tox and testenv sections and is otherwise ignored.
Source: https://tox.readthedocs.io/en/latest/config.html#configuration-discovery
QUESTION
I have a python package, and I am using poetry
for dependency management and packaging.
In my local environment, I am using tox
to test the package in multiple python version.
How can I use GitHub actions to test my package, everytime there is a push or pull request ?
Things that I have tried:
- https://github.com/actions/starter-workflows/blob/main/ci/python-package.yml
(this official action installs via
pip
andrequirements.txt
, but I am using poetry) - https://github.com/abatilo/actions-poetry
(this action, can install poetry, but using
pip
, which is not recommended by poetry, as it can cause conflict with my application dependencies, see issue ) - https://github.com/ymyzk/tox-gh-actions (should I use this ? why not rather run
pytest
in every matrix (of github actions), this action seems to defeat the purpose of tox)
I want to test my python code in gh-actions.
in my situation, what should I actually use ?
what are the best practices ? and most optimum tool
...ANSWER
Answered 2021-Apr-14 at 12:11The beauty of tox
is that you can run it both locally and on CI.
You have a high chance of a successful CI when it passes locally, and also you only need to define the test requirements and the test setup once, in one file.
To do so, I recommend using the mentioned tox-gh-actions
.
I applied this pattern to dozens of repositories with success.
I recommend the following blog post which gives a great introduction to this setup:
https://hynek.me/articles/python-github-actions/
You can have a look at the tox.ini and the gh action config file for e.g. Flask-Reuploaded.
As to your question about running pytest in every matrix... the drawback here is that you need to take care of the test setup yourself, and you have to define everything at two places, tox.ini
for local testing and in the yaml config for gh actions.
QUESTION
Running tox on my python project I receive the following error:
...ANSWER
Answered 2020-Aug-06 at 07:06The problem for me was that I had future in the test deps:
QUESTION
I'm trying to set up codecov monitoring for a public R package, where GitHub Actions will run covr::codecov
. I'm looking at this .yaml example (Source):
ANSWER
Answered 2020-Feb-19 at 14:59No, don't put the token in the .yaml file. For use with GitHub Actions, you add the token to the Secrets section of your GitHub repository, then leave the .yaml code above as it is.
Add the secret at the URL (modify with your names): https://github.com/USERNAME/REPONAME/settings/secrets and call it CODECOV_TOKEN. Then this .yaml code will find it.
(You get the repo's codecov token from https://codecov.io/gh/USERNAME/REPONAME)
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gh-actions
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page