Update dependency pytest-helm-charts to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pytest-helm-charts	~=0.6.0 -> ~=1.2.0

---

Release Notes

giantswarm/pytest-helm-charts (pytest-helm-charts)

v1.2.0

Compare Source

• added:
  • make flux resource ready state check timeouts configurable, still default to 30s

v1.1.2

Compare Source

• changed:
  • dependency updates

v1.1.1

Compare Source

• fixed:
  • the kubectl() method was not capturing standard error stream
• changed:
  • the kubectl() method allows now to be executed within a shell (parameter use_shell, False by default)

v1.0.3

Compare Source

v1.0.2

Compare Source

• fixed:
  • remove defaults for cmd line options - they were breaking env variable options loading

v1.0.1

Compare Source

• changed:

  • _flux_cr_ready made public by renaming to flux_cr_ready
  • Test information data is now primarily being input by (partially mandatory) environment variables.
    Majority of old command line parameters should still work, but environment variables usage is encouraged.
    This allows pytest-helm-charts to be easily used without the app-test-suite
    project, which was enforcing the cmd line parameters before. The following env vars are recognised and used in
    fixtures (when requested):
    • "KUBECONFIG" - (mandatory) a path to kube config file used to connect to a k8s cluster
    • "ATS_CHART_PATH" - path to a chart being tested (if a chart is tested)
    • "ATS_CHART_VERSION" - version of the chart being tested (if a chart is tested)
    • "ATS_CLUSTER_TYPE" - (informative only) type of the cluster used for testing
    • "ATS_CLUSTER_VERSION" - (informative only) k8s version of the cluster used for testing
    • "ATS_APP_CONFIG_FILE_PATH" - optional path to a values.yaml file used to configure a chart under test
      (if a chart is tested)
    • "ATS_EXTRA_*" - any such arbitrary variable value will be extracted and included in the test_extra_info fixture
  • chart_extra_info fixture was removed, as the more general test_extra_info is available

• updated:

  • pytest upgraded from 6.x series to 7.x

v0.7.1

Compare Source

• fixed:
  • 'repositories' attribute of Catalog CR is now handled

v0.7.0

Compare Source

• changed:
  • all the changes from beta releases below
  • fixed docs issues

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: tests/ats/Pipfile.lock

Command failed: docker run --rm --name=renovate_a_sidecar --label=renovate_a_child --memory=3584m -v "/tmp/worker/c3073a/f6b948/repos/github/giantswarm/kyverno-policies":"/tmp/worker/c3073a/f6b948/repos/github/giantswarm/kyverno-policies" -v "/tmp/worker/c3073a/f6b948/cache":"/tmp/worker/c3073a/f6b948/cache" -e PIPENV_CACHE_DIR -e PIP_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/tmp/worker/c3073a/f6b948/repos/github/giantswarm/kyverno-policies/tests/ats" ghcr.io/containerbase/sidecar:9.20.2 bash -l -c "install-tool python 3.9.18 && install-tool pipenv 2023.9.8 && pipenv lock"
Creating a virtualenv for this project...
Pipfile: /tmp/worker/c3073a/f6b948/repos/github/giantswarm/kyverno-policies/tests/ats/Pipfile
Using /opt/containerbase/tools/python/3.9.18/bin/python3.9 (3.9.18) to create virtualenv...
created virtual environment CPython3.9.18.final.0-64 in 807ms
  creator CPython3Posix(dest=/home/ubuntu/.local/share/virtualenvs/ats-D1pCbm8l, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/ubuntu/.local/share/virtualenv)
    added seed packages: pip==23.2.1, setuptools==68.2.0, wheel==0.41.2
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /home/ubuntu/.local/share/virtualenvs/ats-D1pCbm8l
Locking [packages] dependencies...
False
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot install -r /tmp/pipenv-zjx8b_z_-requirements/pipenv-98lgf81l-constraints.txt (line 5) and pykube-ng~=21.10.0 because these package versions have conflicting dependencies.
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/resolver.py", line 645, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/resolver.py", line 612, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/resolver.py", line 592, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/utils/resolver.py", line 897, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = actually_resolve_deps(
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/utils/resolver.py", line 670, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/utils/resolver.py", line 447, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv run pip install <requirement_name> to bypass this mechanism, then run $ pipenv graph to inspect the versions actually installed in the virtualenv.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Traceback (most recent call last):
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/bin/pipenv", line 8, in <module>
    sys.exit(cli())
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/cli/options.py", line 58, in main
    return super().main(*args, **kwargs, windows_expand_args=False)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/vendor/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/cli/command.py", line 340, in lock
    do_lock(
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/routines/lock.py", line 65, in do_lock
    venv_resolve_deps(
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/utils/resolver.py", line 838, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
  File "/opt/containerbase/tools/pipenv/2023.9.8/3.9/lib/python3.9/site-packages/pipenv/utils/resolver.py", line 707, in resolve
    raise RuntimeError("Failed to lock Pipfile.lock!")
RuntimeError: Failed to lock Pipfile.lock!

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.