Target selectors docs

[phanimarupaka]

No description provided.

[frankfarzan]

I find this counter-intuitive. I expected specifying mysql would include its subpackages. It's probably a more common use case to want to select the entire package hierarchy under mysql, no? With this model, how do you specify that? Is the thinking that there'll be a wildcard syntax?

[frankfarzan]

@droot

[phanimarupaka]

We discussed about this and the point is about the default behavior and what makes it more intuitive to users. How about making what you mentioned a default behavior. If users wants to specifically exclude subpackages we can include a new field called excludeSubpackages.

So shall I reimplement this to make it package instead of packagePath and accept full package identifiers with no wild cards support ? Where default behavior is to include all the subpackages?

[frankfarzan]

To unblock the rest of the feature, you can leave packagePath out of the documentation, and address it separately. Design discussions are better done in a design doc where you can evaluate the overall UX and consider alternatives. There's also a related discussion about globbing support across all matchers. target field in Kustomize patch support wildcards, has this been discussed anywhere?

[droot]

So closing the loop here, @phanimarupaka and me had an offline discussion about it. We agree the current behavior is unintuitive, So we are going to disable packagePath selector for now and re-introduce it with along with subpackage exclusion functionality later.

[frankfarzan]

Approved after removing packagePath and following up on open questions.