Show user details with the corresponding builder actions

[sajjaphani]

Habitat users can perform various actions (upload, trigger a build, promote, etc.) on the builder through the CLI or the Web UI. Some of these actions can also be triggered by some external software (CI tool, for example).

Currently, the builder does not have any functionality to show the user data on the Web UI.

It will be helpful to include the user details on the Web UI or in the APIs.

Below are the few places where including the user details:

• Package level promotions
• Package Versions
• Build Job
• Package Settings
• Builder Events

[sajjaphani]

core origin is managed by the packages refresh team (Chef/Progress), the details do not matter to the end-user.

Similarly, chef origin is managed by Chef/Progress and does not matter to the end consumer. However, the packages within chef origin are being maintained by different teams it will be useful to show user information.

For all other origins, private or public, which are typically created/ managed by external users, show the user details.

When to show the user details?

1: For private origin/package user can only see the details if he has access to that origin/package (after login). 2. For public origin/package

1. Show user details by default.
2. Show the user details only when they log in.

For public origin/packages (public SaaS), show the user details irrespective of the user is logged in or not. Users will be using their GitHub account to log in.

What user info to show? Username, email?

The same applies to on-prem environment.

[sajjaphani]

Initially, we can target the following pages to add the user details:

1. Channels List in package page
2. Build Jobs
3. Builder Events

We will add a new column to show the user details. As an example, the below image shows the user details for the channels.

[rahulgoel1]

@sajjaphani I spoke with Mark dennard and suggestion is to change " User" to "Promoted/Demoted By" . It will indicate better usability for users.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.