Change Details

[Currently as email exchange] First check on staging and then reiterate the procedure on production when ready. Plan, staging first (TODO: find the docs links and report them here): - [X] ~~swh: provide documentation on actions to undertake by clients (and push them to the clients)~~z. None exists ¯\_(ツ)_/¯ - [X] Reply to email asking for required information: - [X] keycloak staging user to create on staging - [X] provider url - [x] D8142: Create documentation on how to boostrap a new deposit collection - [x] Send email to require the needed information [1] - [ ] awaiting feedback from client - [ ] client: Create account on keycloak staging - [ ] client: provide a provider url - [ ] swh: Create deposit collection for new deposit client - [ ] swh: associate the provider url to the new deposit client - [ ] check: client: push their first deposit following api documentation [1] email excerpt ``` ... All, just so you know, we'll start by checking out everything goes fine in the staging instance first. We'll then move on to repeat the process in production once all papercuts are lifted. > May you provide them with the crenentials to access the deposit interface? Sure. It's no longer an swh action now though, it's a client one. First they need to create an account on our (staging) keycloak instance [1] ("New User? register" link). Then report here what's their login so I can create the associated deposit collection (i'll name it "oin" if you are fine with it) in the deposit instance. Could you also please provide a provider url? That'd be a namespace url you own to which we expect to receive your artifacts from [2] (required information the deposit server will check when you post deposits). This information is also associated to your deposit client. [0] https://forge.softwareheritage.org/T4399 [1] https://webapp.staging.swh.network/oidc/login/?next_path=https://webapp.staging.swh.network/ [2] https://docs.softwareheritage.org/devel/swh-deposit/specs/protocol-reference.html?highlight=provider_url#semantics-of-origin-urls ```

[Currently as email exchange] First check on staging and then reiterate the procedure on production when ready. Plan, staging first (TODO: find the docs links and report them here): - [X] ~~swh: provide documentation on actions to undertake by clients (and push them to the clients)~~. None exists ¯\_(ツ)_/¯ - [X] Reply to email asking for required information: - [X] keycloak staging user to create on staging - [X] provider url - [x] D8142: Create documentation on how to boostrap a new deposit collection - [x] Send email to require the needed information [1] - [x] Publish new documentation to register new deposit client [3] - [ ] (current status) awaiting feedback from client - [ ] client: Create account on keycloak staging - [ ] client: provide a provider url - [ ] swh: Create deposit collection for new deposit client - [ ] swh: associate the provider url to the new deposit client - [ ] check: client: push their first deposit following api documentation [1] email excerpt ``` ... All, just so you know, we'll start by checking out everything goes fine in the staging instance first. We'll then move on to repeat the process in production once all papercuts are lifted. > May you provide them with the crenentials to access the deposit interface? Sure. It's no longer an swh action now though, it's a client one. First they need to create an account on our (staging) keycloak instance [1] ("New User? register" link). Then report here what's their login so I can create the associated deposit collection (i'll name it "oin" if you are fine with it) in the deposit instance. Could you also please provide a provider url? That'd be a namespace url you own to which we expect to receive your artifacts from [2] (required information the deposit server will check when you post deposits). This information is also associated to your deposit client. [0] https://forge.softwareheritage.org/T4399 [1] https://webapp.staging.swh.network/oidc/login/?next_path=https://webapp.staging.swh.network/ [2] https://docs.softwareheritage.org/devel/swh-deposit/specs/protocol-reference.html?highlight=provider_url#semantics-of-origin-urls ``` [3] https://docs.softwareheritage.org/devel/swh-deposit/api/register-account.html

[Currently as email exchange] First check on staging and then reiterate the procedure on production when ready. Plan, staging first (TODO: find the docs links and report them here): - [X] ~~swh: provide documentation on actions to undertake by clients (and push them to the clients)~~z. None exists ¯\_(ツ)_/¯ - [X] Reply to email asking for required information: - [X] keycloak staging user to create on staging - [X] provider url - [x] D8142: Create documentation on how to boostrap a new deposit collection - [x] Send email to require the needed information [1] - [ ]- [x] Publish new documentation to register new deposit client [3] - [ ] (current status) awaiting feedback from client - [ ] client: Create account on keycloak staging - [ ] client: provide a provider url - [ ] swh: Create deposit collection for new deposit client - [ ] swh: associate the provider url to the new deposit client - [ ] check: client: push their first deposit following api documentation [1] email excerpt ``` ... All, just so you know, we'll start by checking out everything goes fine in the staging instance first. We'll then move on to repeat the process in production once all papercuts are lifted. > May you provide them with the crenentials to access the deposit interface? Sure. It's no longer an swh action now though, it's a client one. First they need to create an account on our (staging) keycloak instance [1] ("New User? register" link). Then report here what's their login so I can create the associated deposit collection (i'll name it "oin" if you are fine with it) in the deposit instance. Could you also please provide a provider url? That'd be a namespace url you own to which we expect to receive your artifacts from [2] (required information the deposit server will check when you post deposits). This information is also associated to your deposit client. [0] https://forge.softwareheritage.org/T4399 [1] https://webapp.staging.swh.network/oidc/login/?next_path=https://webapp.staging.swh.network/ [2] https://docs.softwareheritage.org/devel/swh-deposit/specs/protocol-reference.html?highlight=provider_url#semantics-of-origin-urls ``` [3] https://docs.softwareheritage.org/devel/swh-deposit/api/register-account.html