Simple deployment request/responding provider filtering scheme #924

New Issue

dboreham · 2024-08-15T16:58:00Z

dboreham commented

2024-08-15 16:58:00 +00:00

From Slack:

There's two related upgrades to the deployer system would be helpful to have:

Ability to blacklist/whitelist name authorities. With rich regex so one can specify in the .env , for example WHITELIST=*german-users-only so that deployer instance would only deploy ApplicationDeploymentRequests coming from name authorities that end in german-users-only
Users specifying in the ApplicationDeploymentRequest which SPs they want to deploy to. Same idea as 1 but this way users don't end up deploying 10 versions of the same app to 10 SPs
Because right now, every deployer instance will deploy every ApplicationDeploymentRequest

@zramsay (edited to specify 1 & 2)

From Slack: There's two related upgrades to the deployer system would be helpful to have: 1. Ability to blacklist/whitelist name authorities. With rich regex so one can specify in the .env , for example WHITELIST=*german-users-only so that deployer instance would only deploy ApplicationDeploymentRequests coming from name authorities that end in german-users-only 2. Users specifying in the ApplicationDeploymentRequest which SPs they want to deploy to. Same idea as 1 but this way users don't end up deploying 10 versions of the same app to 10 SPs Because right now, every deployer instance will deploy every ApplicationDeploymentRequest @zramsay (edited to specify 1 & 2)

dboreham commented

2024-08-15 19:16:02 +00:00

There is existing support for filtering deployment requests against specified include and exclude tag value sets:

https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/stack_orchestrator/deploy/webapp/deploy_webapp_from_registry.py#L431

There is existing support for filtering deployment requests against specified include and exclude tag value sets: https://git.vdb.to/cerc-io/stack-orchestrator/src/branch/main/stack_orchestrator/deploy/webapp/deploy_webapp_from_registry.py#L431

dboreham commented

2024-08-15 20:44:11 +00:00

Updated doc on the existing deployment filtering features: https://www.notion.so/Deploying-Laconic-Webapps-from-the-Registry-to-Kubernetes-46a612ed6faa4146abc1eeac7960eb2d?pvs=4#cb74b9fcb729497b8b7e7408b6bb7e61

dboreham commented

2024-08-15 21:19:50 +00:00

Additional functionality requested:

Deployer can optionally check for payment associated with a deployment request, and deny any request that lacks associated payment.
This presumably could be done by the deployment requestor first making a token transfer to the deployer's address (which it knows through out of scope means). Then the deployment requestor places a reference to that transfer in the deployment request record.

One problem here is that we need to exclude replay attacks -- the deployer must mark each transfer to itself as consumed, somehow once the requested app is deployed. This could be done by cross referencing new requests' payment transfers vs old already-completed deployments.

Additional functionality requested: Deployer can optionally check for payment associated with a deployment request, and deny any request that lacks associated payment. This presumably could be done by the deployment requestor first making a token transfer to the deployer's address (which it knows through out of scope means). Then the deployment requestor places a reference to that transfer in the deployment request record. One problem here is that we need to exclude replay attacks -- the deployer must mark each transfer to itself as consumed, somehow once the requested app is deployed. This could be done by cross referencing new requests' payment transfers vs old already-completed deployments.

dboreham commented

2024-08-16 21:00:21 +00:00

Closing this issue, opened new one to address specifically paid deployment: #927

Closing this issue, opened new one to address specifically paid deployment: https://git.vdb.to/cerc-io/stack-orchestrator/issues/927

dboreham closed this issue

2024-08-16 21:00:21 +00:00

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#924