Account A is a service provider who has registered a name authority. This account can deploy apps via the deployer as expected.
Account B is a user who wishes to publish a webapp to that service provider. This account doesn't have permission to do so. They must instead register a sub authority.
Account B must communicate to Account A that they wish to register a sub authority. Account B provides their chosen sub authority and laconic address to Account A.
Account B runs `laconic registry authority bond set met2.lcn-example <account_B_bond_id>
Account B can now configure a PWA repo via existing tooling to publish an ApplicationRecord and ApplicationDeploymentRequest, where the name field in package.json includes the sub authority (e.g., "name": "@met2.lcn-example/my-webapp")
The deployer run by Account A picks up this request: Generating name pwa-test-6-773ce7ac36 for request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu. cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.
but it does not build or deploy it, or do anything with this request. This issue is to address 1) build and deploy any ApplicationDeploymentRequest published as a sub authority (main priority) and 2) re-work the tooling to automate the granting of a sub authority.
Description:
Account A is a service provider who has registered a name authority. This account can deploy apps via the deployer as expected.
Account B is a user who wishes to publish a webapp to that service provider. This account doesn't have permission to do so. They must instead register a sub authority.
Account B must communicate to Account A that they wish to register a sub authority. Account B provides their chosen sub authority and laconic address to Account A.
Account B creates a bond.
Account A runs: `laconic registry authority reserve me.lcn-example --owner laconicAccountB` then,
Account B runs `laconic registry authority bond set met2.lcn-example <account_B_bond_id>
Account B can now configure a PWA repo via existing tooling to publish an ApplicationRecord and ApplicationDeploymentRequest, where the name field in package.json includes the sub authority (e.g., "name": "@met2.lcn-example/my-webapp")
The deployer run by Account A picks up this request: `Generating name pwa-test-6-773ce7ac36 for request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu.
cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.`
but it does not build or deploy it, or do anything with this request. This issue is to address 1) build and deploy any ApplicationDeploymentRequest published as a sub authority (main priority) and 2) re-work the tooling to automate the granting of a sub authority.
dboreham
was assigned by AFDudley2024-08-14 13:33:00 +00:00
This is required because we've had to change the testnet plan.
Given how close Zach's hacks were to completing this, it seems like Thomas should be able to complete this before friday, assuming he's working at all. It needs to be done by monday so @dboreham please assign this to Ashwin if you folks can't get it done in time. Thanks so much.
This is required because we've had to change the testnet plan.
Given how close Zach's hacks were to completing this, it seems like Thomas should be able to complete this before friday, assuming he's working at all. It needs to be done by monday so @dboreham please assign this to Ashwin if you folks can't get it done in time. Thanks so much.
cerc-webapp-deployer: Generating name pwa-test-6-773ce7ac36 for request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu.
cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.
cerc-webapp-deployer: Skipping request bafyreihsu72hvy4bcghbsi27rruehxd2s76qk4lfo5hs4rdadtp6lu253y, cannot locate app.
More log from Slack:
```
cerc-webapp-deployer: Generating name pwa-test-6-773ce7ac36 for request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu.
cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.
cerc-webapp-deployer: Skipping request bafyreihsu72hvy4bcghbsi27rruehxd2s76qk4lfo5hs4rdadtp6lu253y, cannot locate app.
```
First, the deployment error probably has nothing to do with the registry namespace issues.
Second, deployer logging makes it hard to see but there are two deployment requests in play. One fails due to the app record not being found. This is expected. The second fails for unknown reasons. The only log output we have for that request is this:
cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.
Nothing is logged after this point, although there is a log line to do with the subsequent request, implying that the deployer didn't outright crash.
Update:
First, the deployment error probably has nothing to do with the registry namespace issues.
Second, deployer logging makes it hard to see but there are two deployment requests in play. One fails due to the app record not being found. This is expected. The second fails for unknown reasons. The only log output we have for that request is this:
```
cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.
```
Nothing is logged after this point, although there is a log line to do with the subsequent request, implying that the deployer didn't outright crash.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dboreham
Description:
Account A is a service provider who has registered a name authority. This account can deploy apps via the deployer as expected.
Account B is a user who wishes to publish a webapp to that service provider. This account doesn't have permission to do so. They must instead register a sub authority.
Account B must communicate to Account A that they wish to register a sub authority. Account B provides their chosen sub authority and laconic address to Account A.
Account B creates a bond.
Account A runs:
laconic registry authority reserve me.lcn-example --owner laconicAccountBthen,Account B runs `laconic registry authority bond set met2.lcn-example <account_B_bond_id>
Account B can now configure a PWA repo via existing tooling to publish an ApplicationRecord and ApplicationDeploymentRequest, where the name field in package.json includes the sub authority (e.g., "name": "@met2.lcn-example/my-webapp")
The deployer run by Account A picks up this request:
Generating name pwa-test-6-773ce7ac36 for request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu. cerc-webapp-deployer: Found request bafyreiejppbod2sqw5qtbxhz7gam4cwb7en6zakuwqlnf5z3q6jo5i5hcu to run application lrn://met2.lcn-example/applications/pwa-test-6@0.1.22 on pwa-test-6-773ce7ac36.but it does not build or deploy it, or do anything with this request. This issue is to address 1) build and deploy any ApplicationDeploymentRequest published as a sub authority (main priority) and 2) re-work the tooling to automate the granting of a sub authority.
This is required because we've had to change the testnet plan.
Given how close Zach's hacks were to completing this, it seems like Thomas should be able to complete this before friday, assuming he's working at all. It needs to be done by monday so @dboreham please assign this to Ashwin if you folks can't get it done in time. Thanks so much.
1 sounds straightforward. Which tooling are we describing in 2?
More log from Slack:
This error appears to be to do with the record with name
lrn://met2.lcn-example/applications/pwa-test-6@0.1.22not resolving in the registry.and
Update:
First, the deployment error probably has nothing to do with the registry namespace issues.
Second, deployer logging makes it hard to see but there are two deployment requests in play. One fails due to the app record not being found. This is expected. The second fails for unknown reasons. The only log output we have for that request is this:
Nothing is logged after this point, although there is a log line to do with the subsequent request, implying that the deployer didn't outright crash.
Deployer status: https://webapp-deployer-ui.pwa.realitynetwork.store/