hi everyone i have a question about the helm backend and dep

Question

hi everyone i have a question about the helm backend and dependency inference thread

narrow-judge-15725 · Answer

in the documentation it states for it to work one just needs to add a `source root` my setup is something like pants toml ``` source root patterns = src infrastructure helm charts ``` src infrastructure helm charts base Chart yaml ```apiVersion v2 description Common utilities for helm charts name base version 1 0 0``` src infrastructure helm=charts core Chart yaml ```apiVersion v2 description Core dependencies for any kubernetes cluster name core version 1 0 0 dependencies name base``` Each folder has the build file which tailor generated correctly As per the documentation this should be sufficient for the base dependency to be discovered from core But ``` pants dependencies src infrastructure helm charts core``` Returns nothing

narrow-judge-15725 · Answer

What am i missing Thanks in advance

happy-kitchen-89482 · Answer

Just a guess but what happens if you make your source root `src infrastructure helm charts` without the ` `

happy-kitchen-89482 · Answer

Setting the root to `src infrastructure helm charts ` means that every folder under `helm charts` is a separate root which is probably not what you intended

narrow-judge-15725 · Answer

oh i see then i got confused by the documentation

narrow-judge-15725 · Answer

unfortunately i get the same result after changing this disappointed

narrow-judge-15725 · Answer

``` source root patterns = pants plugins src infrastructure helm charts ```

narrow-judge-15725 · Answer

Screenshot 2022 08 11 at 17 35 41 png

narrow-judge-15725 · Answer

that s my folder structure service should depend on base ```apiVersion v2 name service description Deploys a microservice application version 1 0 0 dependencies name base```

narrow-judge-15725 · Answer

i was trying to follow <https www pantsbuild org docs helm overview chartyaml dependencies|this> part

happy-kitchen-89482 · Answer

cc < witty family 13337> I think you re best placed to help out here

witty-family-13337 · Answer

your source root pattern should be `src infrastructure helm charts `

hundreds-father-404 · Answer

It sounds like that was their original setting in the top of the thread

witty-family-13337 · Answer

right sorry I think I know what is happening

witty-family-13337 · Answer

what version of Pants are you using any chance you could test this with latest SHA from pants repo

witty-family-13337 · Answer

the was an oversight issue with previous release in which the dependency inference rules where not registered when enabling the backend

witty-family-13337 · Answer

it s fixed in `main` and could backport it into 2 13

happy-kitchen-89482 · Answer

So every dir under `src infrastructure helm charts ` should be a root for them That went against my intuition so good thing I cc d you slightly smiling face

witty-family-13337 · Answer

yeah that s right in essence the location of the `Chart yaml` is the root

hundreds-father-404 · Answer

gt it s fixed in main and could backport it into 2 13 Yeah I think that d be helpful given that 2 14 is a few weeks out at lesat

witty-family-13337 · Answer

it s a very small fix so I will get a PR ready

narrow-judge-15725 · Answer

thanks for the help this is a fresh repo ```pants version = 2 12 0 ```

witty-family-13337 · Answer

oh I see would need to backport it to 2 12 too

narrow-judge-15725 · Answer

i can try what you need but 2 12 is what the quickstart script is generating slightly smiling face

narrow-judge-15725 · Answer

i tried with `2 14 0 dev5` and ` ` and it works

narrow-judge-15725 · Answer

``` pants dependencies src infrastructure helm charts service 19 42 07 55 INFO Initializing scheduler 19 42 07 86 INFO Scheduler initialized src infrastructure helm charts base base```

witty-family-13337 · Answer

great so it is what I suspected

narrow-judge-15725 · Answer

it also works with `src infrastructure helm charts` as root through thinking face

narrow-judge-15725 · Answer

should there be a difference

witty-family-13337 · Answer

to resolve dependency it works regardless

narrow-judge-15725 · Answer

if you need a playground i can just share the full thing it is a fresh repo just with this helm stuff

witty-family-13337 · Answer

but if you don t include the then the final chart package will include the root folder inside the tarball

narrow-judge-15725 · Answer

oh understood thumbsup

witty-family-13337 · Answer

and that s going to cause issues with other Helm operations

witty-family-13337 · Answer

I ll try to get a backport asap as soon as I get home I m at my phone right now in the middle of a training session sweat smile

narrow-judge-15725 · Answer

no rush so then the docs are correct it was an actual bug correct

witty-family-13337 · Answer

yup it s a bug

narrow-judge-15725 · Answer

dope thanks for the quick help do you need me to test in other versions or anything else or you already have all you need

witty-family-13337 · Answer

no worries it s a 1 line change that I totally overlooked

narrow-judge-15725 · Answer

unrelated question how would i be able to do `helm template` i should write my own goal for this or there is already a way

witty-family-13337 · Answer

no any actual way right now that would come with 2 14 as it adds support for deployments

witty-family-13337 · Answer

if you could describe your use case I can try to make it available

narrow-judge-15725 · Answer

just printing the result or writing it to a file might be helpful for debugging

witty-family-13337 · Answer

I was thinking of adding it as part of the `export codegen` goal

witty-family-13337 · Answer

but it may take a while as I stabilise the implementation for supporting deployments

narrow-judge-15725 · Answer

hm sorry i m not familiar enough with pants in general sort of started today but maybe it makes sense grin

witty-family-13337 · Answer

this is because rendering a chart requires some of the machinery that is used in the deployments implementation

narrow-judge-15725 · Answer

is this `deployments` something with the helm implementation or something intended to become some kind of pants primitive where can i read more about it

narrow-judge-15725 · Answer

witty-family-13337 · Answer

yeah that s it

narrow-judge-15725 · Answer

ah i see the doc so deployment will be a way of grouping templates to values to do env specific stuff etc no

narrow-judge-15725 · Answer

then yes i think some dry run or knowing what might get deployed if you do trigger the new `deploy` goal would be beneficial

witty-family-13337 · Answer

dry run was another option

witty-family-13337 · Answer

I ll get the backport first then continue on polishing this deployment support for 2 14

narrow-judge-15725 · Answer

i was somewhat coming from bazel and read <https dev to benbirt the right way to install helm charts 4mjp|this> back in the day i think it is a sensible way of doing things and may serve as inspiration in short rule for rendering input chart + values output rendered yaml rule for deploying input the yaml i liked this approach because one can plumb whatever in between for example the deploy rule could take my own yaml or one generated by helm or kustomize or whatever

witty-family-13337 · Answer

deployments will come as an experimental feature in 2 14 happy to gather feedback as we roll it out

witty-family-13337 · Answer

the implementation right now is based on helm install though

narrow-judge-15725 · Answer

amazing

witty-family-13337 · Answer

Backports of the fix for chart dependency inference for Pants 2 12 and Pants 2 13

narrow-judge-15725 · Answer

thanks for working on this

narrow-judge-15725 · Answer

should this work on `pants version = 2 12 0 ` or not yet

narrow-judge-15725 · Answer

oh i see GH actions is still working on it

witty-family-13337 · Answer

I guess it will be part of 2 12 1 release

happy-kitchen-89482 · Answer

Yep we ll do some point releases soon

happy-kitchen-89482 · Answer

maybe even today

happy-kitchen-89482 · Answer

For Slack historians this fix from Alonso gets rid of source root configuration entirely for Helm <https github com pantsbuild pants pull 16531>

happy-kitchen-89482 · Answer

Since we know what the source root has to be the dir of the Chart yaml why force you to configure it Great work < witty family 13337>