Linting fails when using a module that's installed via pip about ansible-lint-action HOT 8 CLOSED

It's probably because this action runs in the container.

from ansible-lint-action.

Yea, that makes sense. it would be good to have a way to run it for these modules though, since there are many that are installed via pip.

from ansible-lint-action.

@aodj is your Workflow Python-based?

from ansible-lint-action.

@aodj is your Workflow Python-based?

Which workflow? Are you referring to the GitHub workflow?

from ansible-lint-action.

Yes

from ansible-lint-action.

Well, I'm using Ansible and pip since the ansible-modules-hashivault library that I mentioned originally isn't fully functional when installed using ansible-galaxy. Here's the configuration I'm using:

name: CI

on: [push]

jobs:
  build:

    runs-on: ubuntu-latest
    
    steps:
    - uses: actions/checkout@v1
    - name: Install dependencies
      run: |
        pip install -r deps/python.txt
        ansible-galaxy install -r deps/galaxy.yml -p ./roles/ --force
    - name: ansible-lint
      uses: ansible/[email protected]
      env:
        ACTION_PLAYBOOK_NAME: main.yml

from ansible-lint-action.

@aodj you're doing pip install in the host VM but the action runs in a docker container that's isolated from whatever you do there.

The action item for us / feature request / would be to accept some arg with a list of deps that we'd then install inside of the container.

from ansible-lint-action.

Alternatively, migrate to js-based action but that'd open up another can of worms like forcing users to pre-configure the proper Python env before using the action.

from ansible-lint-action.