excludeForOperations multiple wildcards doesn't seem to work

[Arch0rr]

Sorry for creating so many issues! 😅
I'm wanting to select all base routes for each tag

POST::/api/<controller1>
POST::/api/<controller2>

While ignoring subroutes

POST::/api/<controller1>/List
POST::/api/<controller1>/Latest

Which I think I should be able to be retrieved by

- openApiOperation: POST::/*
  excludeForOperations:
  - POST::/api/*/*

But this doesn't seem to work. I'm able to use this wildcard string in the filtering file. (I know it's a different package, I just thought it'd be worth noting)

inverseMethods:
- post
operations:
- POST::/api/*/*

Thanks again! 🙌

[thim81]

hi @Arch0rr

I'll investigate if excludeForOperations is supporting wildcards.
We had in mind that exclusions would be very precise.

As a work-around, you could list all the operations in the excludeForOperations, it will be a bit more maintenance but it will be very precise and you know exactly which operations will be excluded. If you would use wildcards, that might lead to unexpected exclusions.

[Arch0rr]

hi @thim81
Sorry I can't test right now, but if I do recall correctly, I was able to do something like

- openApiOperation: POST::/*
  excludeForOperations:
  - POST::/api/Users/*

I believe this worked for the Users tag appropriately, but adding multiple wildcards wasn't working. Again, I can look into doing a well-defined list of exclusions/inclusions before passing the config into portman, which might be safer in the long run. 😃