Alan B

This does break passing in the 'args' from the toml script to the command, but not sure if that was really useful anyway.

Not the OP but maybe i can provide more context. The Prometheus Operator deployed by [kube-prometheus-stack](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack) (and probably other projects) does not support the prometheus.io annotations , and instead uses...

Mad, cuz' i just found this after doing the same thing. Using markdown theme though I was able to integrate it to the bottom of the content section using this...

So far I have not had luck running two different versions of the provider within different modules of the same rootModule, so a way to support 0.x versions of flux...

My current work around is to use the `Git custom command` and `checkout $branch` but would be nice to have a native integration.

This bit me today, luckily didn't impact our prod environment. But i was planning on doing something similar with -beta/-dev/-stage versions of the chart i could test and release to...

Our dev tags follow a pattern like this `version: v0.*-dev` example versions: `0.1.20-dev.1` `0.1.20-dev.2` The idea is we release our dev prerelease chart to services in our dev cluster currently...

> I just ran into this issue and was able to workaround it by using a StateSet > > ```yaml > - name: status_condition > each: > type: StateSet >...

It looks like Netifly checks fail due to unsupported images. I don't think I have any control over this.