Page MenuHomePhabricator

🤔 Metadata for existing instances
Closed, ResolvedPublic

Description

This task enables managers to provide/update information about the purpose, longevity and target audience for already existing instances (previously implemented for new instances here - T384277).

Story

As a product manager, I need to know the intended purpose of instances running on Cloud, in order to understand use cases better and make strategic decisions.

As a manager of an existing instance, I must provide/update information on its intended purpose, longevity and target audience.

Design

Figma file (don't forget to log in with the WBC Engineers account to be able to access the dev tools that contain the specs)

Acceptance Criteria

  1. For each existing instance on the dashboard, there is a way to provide information about the instance's intended purpose, longevity and target audience.
  2. The questions are the same as implemented in T384277.
  3. The condition for having to answer the 'target audience' question is the same (it's only relevant for data hubs).
  4. If the user already answered these questions previously (during instance creation or on this form), the selected options and answers are visible there.
  5. If one or more of the questions are yet unanswered, the user is notified about this in UI and is nudged towards answering them.

Event Timeline

Anton.Kokh updated the task description. (Show Details)
Anton.Kokh updated the task description. (Show Details)
Anton.Kokh updated the task description. (Show Details)
Anton.Kokh renamed this task from Metadata for existing instances to 🤔 Metadata for existing instances.Mar 12 2025, 10:18 AM

I was claiming that there is a very natural decomposition between frontend and backend for this task.

For the backend we will require a new endpoint that supports PUT (or perhaps POST if more convenient but less semantically correct) to take new WikiProfile objects.

We will also need a new WikiProfile GET endpoint (or to augment the existing WikiController?) to include already set Profile data for the wiki to display.

For the frontend we have discussed if we want to split this up but we are not certain if we want to split it up e.g. with a new tab, then a read only status of the profile, then a write new profile. @dena will pick this up