Repository navigation
Conversation
1de6749 to
b683613
Compare
This reverts commit b683613.
9956cac to
7137218
Compare
| import "google/protobuf/timestamp.proto"; | ||
|
|
||
| // OnBehalfMVMService offers MVM operations on behalf of a customer tenant. | ||
| service OnBehalfMVMService { |
There was a problem hiding this comment.
We also need to add a OnBehalfManagedVM, that outputs the billing information to show it in the clients - with a different GET and LIST endpoint.
There was a problem hiding this comment.
Just introduced that. @Pilzington and @ostempel would you mind taking a look and report how this feels?
There was a problem hiding this comment.
@ma-hartma Not sure what you mean. These endpoints do not exist yet?
There was a problem hiding this comment.
At the moment we don't do any role or permissions in the frontend, so we "just" use the customer view. I have some PR which should streamline and prepare for permissions per product.
Nevertheless you are right @ma-hartma, that we will also need an endpoint to present the information, that only provider or on-behalf can see.
Description
This is a draft for what we discussed. Related to https://github.com/fi-ts/fco-docs/pull/20
This PR tries to tackle multiple problems at once:
OperatorRolewith an additionalrole_contextmethod option that allows adjusting the behavior of tenant / project / product rolesROLE_CONTEXT_UNSPECIFIEDno restrictionsROLE_CONTEXT_PROVIDERthe tenant must be the provider tenantROLE_CONTEXT_ON_BEHALFthe user must be in the provider tenant, the target tenant might differfits_mvm-all#all-all-admin) usingrole_context = ROLE_CONTEXT_ON_BEHALFfits_pcvm-all-all-admin) usingrole_context = ROLE_CONTEXT_PROVIDERfits_fcoconf-all-all-adminfuture to store tenant accounting data) usingrole_context = ROLE_CONTEXT_PROVIDER*_provider.protoor*_on_behalf.proto(e.g.mvm_on_behalf.proto); public files must not carry the option at allOnBehalfMVMService)Test_RoleContextin the api repo