I would like to be able to use wildcards when declaring depe

Question

I would like to be able to use wildcards when declaring dependencies in a BUILD file For context we have a bunch of django apps in one repo which are part of one django project When running migrations I would like to be able to depend on `src django apps migrations` but it seems that I can t do that in a BUILD file Is there a good way around this Or will we need to manually manage that list

wide-midnight-78598 · Answer

Can you give an example of what your BUILD file might look like I assume each of these migrations are py files Like is there anything wrong with using the `files` or `resources` target and depending on that

wide-midnight-78598 · Answer

loud-laptop-17949 · Answer

i have resource targets for each of the migrations directories i just have 42 of them

loud-laptop-17949 · Answer

and I need manage py to depend on all of them

loud-laptop-17949 · Answer

i want to be able to write a build file like ```python sources pex binary name= manage entry point= manage py dependencies= src django apps migrations migrations ```

loud-laptop-17949 · Answer

but the ` ` in the middle won t work as a wildcard

wide-midnight-78598 · Answer

So if you had a resources or files target with a glob to grab your migration files that won t work for your usecase

wide-midnight-78598 · Answer

More specifically something like this ```files name= mymigrationstuff sources= migrations py This is just here so I could sanity test this glob archive name= arch format= zip files= mymigrationstuff ```

loud-laptop-17949 · Answer

yeah I think the problem with that is that I will end up with overlapping file ownership

loud-laptop-17949 · Answer

like I already have targets for all these files I just need to depend on a large number of targets

wide-midnight-78598 · Answer

Ah okay then I m less sure of a solution

eager-dress-66405 · Answer

Would we be able to write a small target plugin that determined the deps for us using our own logic

hundreds-father-404 · Answer

Hey late to this thread but check out discussion at Yes < eager dress 66405> see near the end of the thread for instructions on how to do so slightly smiling face I m definitely curious y alls feedback on Josh s `dependencies globs` field the idea of having a distinct field is a really interesting one imo that resolves my major concern

eager-dress-66405 · Answer

How timely A plug in that would add a dependency globs field to existing targets without further overloading the target syntax is both a very clever solution and a great example of the flexibility of the plug in system

hundreds-father-404 · Answer

Definitely if folks are interested there s potential for `dependency globs` moving into Pants core A big question I d have is whether `dependency globs` should be sources paths gt finding the `Owners` of those sources vs some new glob syntax for `Address`es That new glob syntax is what I m less confident on given how complex Address syntax already is I don t love the idea of inventing Yet Another Syntax to learn I guess we do have `dir ` and `dir ` globs for addresses tho

eager-dress-66405 · Answer

I hear you Prefix globs+regex match expressionless What about flipping the relationship add a way for a target to depend on everything with a particular tag

hundreds-father-404 · Answer

I could see a use for that I think what that suggests to me though is this might be one of those times it s too hard to generalize well so instead we have several essentially prebuilt plugin hooks you can copy amp modify That s what we tried to do with the custom `setup py ` kwargs plugin hook for example Unclear to me