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

ct.yaml in workdir overrides "config:" #53

Closed
smlx opened this issue Oct 1, 2020 · 3 comments
Closed

ct.yaml in workdir overrides "config:" #53

smlx opened this issue Oct 1, 2020 · 3 comments

Comments

@smlx
Copy link

smlx commented Oct 1, 2020

I have a ct.yaml in the root of my repo and want to override this for a particular step. I tried this:

    - name: Run chart-testing (lint)
      id: lint
      uses: helm/chart-testing-action@v1.0.0
      with:
        command: lint
        config: test-suite.ct.yaml

This means:

  • test-suite.ct.yaml file is mounted to /etc/ct/ct.yaml inside the container
  • /workdir inside the container contains the ct.yaml from the root of my repo

Due to the precedence rules of chart-testing config files the /workdir/ct.yaml is used instead of /etc/ct/ct.yaml. This was surprising to me.

It seems like reasonable behaviour once I understood what's going on, but it's something of a gotcha. Would you accept a PR documenting this behaviour in the README?

@smlx
Copy link
Author

smlx commented Oct 1, 2020

Forgot to mention the workaround: If you need to have multiple ct.yaml configuration files, name them something other than /ct.yaml, and specify them explicitly for each step.

@davidkarlsen
Copy link
Member

Can you test with v2.0.0? It should avoid this problem altogether.

@cpanato
Copy link
Member

cpanato commented Sep 27, 2022

closing, no response from the submitter

@cpanato cpanato closed this as completed Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants