capabilities billing default_plan

[soxofaan]

openeo-api/openapi.yaml

Lines 720 to 726 in f303d65

	default_plan:
	type: string
	description: >-
	Name of the default plan to use when the user doesn't
	specify a plan or has no default plan has been assigned
	for the user.
	example: free

first, a small typo:

... or has no default plan has been assigned ...

While thinking about it, it seems this is not well defined yet:
Should the default plan be a paid or non-paid plan?
If it's a paid plan, then how can it be a default for free users?
If it's a non-paid plan, then it's not ideal to use as default for paying users (e.g. they get worse performance because they are not using their paid plan).

[soxofaan]

(related to #425 )

[soxofaan]

given #425 : maybe there should be no global default plan, and just a per user default plan (based on their subscription)?

[m-mohr]

I've tried to improve documentation in PR #428 based on the situation we have right now.

[jdries]

I'm also really not sure that we'll end up with a notion of multiple billing plans per user.
There's also this vsc4 'plan', which is not really a billing plan but rather an entirely separate backend, which might even have specific capabilities.

[m-mohr]

Sure, but this is the general API so the option should be there anyway. Somewhat agree on vsc4. One the one hand it's a somewhat separate back-end, but on the other hand the billing plans were also meant to distinguish between different "configurations of hardware". So depends on a case by case basis.