Services selectors

[Gabrielbdd]

Is your feature request related to a problem?
No

Which solution do you suggest?
A declarative way to provide selectors for services in one place in the config.yaml

Currently, for use port-fowarding, sync, terminal, and the devspace enter command we should repeatedly provide the selector for the desired service:

devSpace:
  ports:
    - labelSelector:
        app: api
  sync:
    - labelSelector:
        app: api
  terminal:
    labelSelector:
      app: api

and

devspace enter -l app=api

What if we could instead provide a way to map the services with they respective selectors and then just reuse it?
Ex:

services:
  - name: api
    labelSelector:
      app: api
devSpace:
  ports:
    - service: api
  sync:
      service: api
  terminal:
    service: api

and

devspace enter api

or

devspace enter --service api

or

devspace enter -s api

I guess it will be much more clear to write config.yaml file and use the devspace enter command

/kind feature

[LukasGentele]

Thanks for suggesting this enhancement. I think that makes sense especially for users with many services and port/sync configurations. What do you think @FabianKramm?

Your suggestion would also affect the implementation of #267. So far, I have not started working on it because it is not that great to assume certain labels in required helm charts. An alternative would be to add a "service" to the config when a user runs devspace add package [package] with the assumed labels. This approach would allow the user to adjust the labelSelector for this service in the config if it does not match the most common helm labels. I really like that. I'm closing #267 in favor of this feature request.

[KaelBaldwin]

I was close to suggesting something like this as well.

My situation is that I’d like to minimize the amount of info that needs to be overwritten.

Right now overwriting a label selector involves changing it in multiple locations, and because those locations are arrays, they entire object has to be overwritten.

I’m going to end up having multiple developers running a devspace for the same application in the same namespace (so i don’t have to create a namespace for each user) so i need to overwrite the name of the deployment and all the label selectors so they are unique.

Being able to do this is one place would be nice.