Cost Management needs specific pages to be created for OCP source types. Details of the flow can be seen in the UX Mocks here: https://marvelapp.com/4b472gc/screen/62036227

The OCP Cluster ID will be stored in the Platform Sources service in the source_ref field on the sources API.

See project-koku/koku#1319 for some more general details around this.

@rvsia recently implemented the AWS-Cost Management wizard pages and is available to consult on this issue.

@boaz0 would be a great candidate to work on this 👍

@nlcwong Please feel free to include in the right UX person to this issue.

For Cost Management, we are removing all data when the application is removed from the source. The in CI-beta the warning for removing data is happening after the source is destroyed, not the application. At this point it's too and the user just removed their cost-mgmt data before getting warned.

There is future work being discussed around implementing a cost management "soft delete" feature with a data retention policy. That will certainly have implications to this UX (@nlcwong).

For now I wanted to call it out that this warning message should be occurring before the application is removed, not the source with today's cost-platform sources integration.

1. Delete Source with application attached
   

2. Warning message that an application is attached to the source. Gives opportunity to remove.
   

3. Clicks Remove for confirmation box (no warning message yet...). Cost data is removed when the Red Remove button is clicked.
   

4. Remove source confirmation now that all applications are gone. (Cost Management data is already gone at this point)
   

The containerized frontend is looping and throwing a console error on navigation to settings, because sources is the default page for settings.

This was introduced in this change:
#1105

The image for 74f0056 does not display this behavior:
https://quay.io/repository/cloudservices/sources-ui/manifest/sha256:dcd4e252fb22a95a7409b4b413408915519b64fbbbf0df351ce2d48514452356

The image for 84c5520 (merge commit of 1105) does display the looping behavior.
https://quay.io/repository/cloudservices/sources-ui/manifest/sha256:709c3c8b337ad30b23576fd6bbe5685dd7986941d31d330d33ee589b4b815bbe

This can be replicated by deploying to ephemeral using bonfire with the --set-image-tag quay.io/cloudservices/sources-ui=74f0056 option.

Video of the behavior has been shared internally with the maintainers.

Use hooks

• React intl #135
• React router #150
• Redux #136
• React

When runtime error happens, there is no proper UX.

Current behavior

cc @terezanovotna

OCP Cost Management sources are now possible with RedHatInsights/frontend-components#283.

The cluster-id value needs to be editable via the Platform Sources Edit view

revert 81e8132

see nodejs/node#40046

The source creation onboarding wizard flows allow for per-app wizard screens when attaching an application. For example: Create AWS Source with Cost Management attached, the user is prompted to enter the S3 bucket.

The app-specific UI pages are missing when attaching an application to a pre-existing source via the ... -> Manage applications screen.

Changes are needed for AWS, OCP, and Azure

UX considerations should be made for how the user would reuse some of the data that was already added when the source was initially created.

The most complicated situation is AWS. For example, here are some questions that come to mind:

• The roleARN can be added when creating an AWS source, Cost Management needs this, should it reuse the one already added or should it be given an opportunity to be changed? What's the impact of this to other applications if its changed
• How should the user handle the fact that they can not see the current roleARN due to backend implementation details?
• If the source had a AWS Secret added and no roleARN, we would need them to add a roleARN for Cost Management since we do not currently support AWS secret keys. Are there any sources backend implications to having both an AWS secret and a roleARN?

FYI: @nlcwong

New cost management Sources API was added with project-koku/koku#1481.

Please move the AWS bucket API calls to use the new API.

Once done we can merge project-koku/koku#1548 to remove the old APIs.

Description

Show errors from API calls in notifications

@miq-bot assign @rvsia

@Hyperkid123

This is a table which shows how the UI maps values obtained by API to the icon which is shown to an user in the table list.

When I was working on this, I didn't know that the top-level is not always representing the updated status. I thought that the top level status is just some aggregation of its application status. (i.e.: All apps are connected > available, some app is not available > partially available, no apps is available > unavailable, no app is connected > unavailable)

So, I will be happy if you can help me to complete this table with backend/api information I haven't got (or I got wrong).

Question:

Can be source available/unavailable when there is no application attached? If yes what connects to it?

@agrare @gtanzillo @dccurtis

cc @terezanovotna

Cost Management needs specific pages to be created for Azure source types. Details of the flow can be seen in the UX Mocks here: https://marvelapp.com/4b472gc/screen/62036219 (mocks need to have the resource group, storage account and subscription ID added still)

The Azure Resource Group, Storage Account, and Subscription ID will be added to the Cost Management service and the Tenant ID, Client Secret, and Client ID will be added to Platform Sources

Storage Account and Resource Group can be added to cost management with the billing_source API

JSON POST example:
{"source_id": 1, "billing_source": {"data_source": { "resource_group": "MYRG", "storage_account": "testaccount"}}}

Subscription ID can be added to cost management with the authentication API

JSON POST example
{"source_id": 3, "credentials": {"subscription_id": "cffa2d90-8507-4817-a5a1-279555f83704"}}

The Platform Source values for tenant id, client secret, and client id would remain as they are today.

@rvsia recently implemented the AWS-Cost Management wizard pages and is available to consult on this issue.

@boaz0 would be a great candidate to work on this 👍

@nlcwong Please feel free to include in the right UX person to this issue.

Hi @terezanovotna, there is one confusing behaviour when managing applications in Sources.
When I remove one or more applications, then I must click to "Cancel" link.
It can be taken that my changes will be reverted.

Based on UX session

• cancel hover on uneditable fields
• grid 6 > 12
• checkboxes/switches no pencil icon

The Cost Management AWS edit screen can now send bucket updates to the cost management service using API introduced here project-koku/koku#1481

Azure Cost Management source wizard pages are being created with RedHatInsights/frontend-components#294

The Source Edit screen should allow for all of the values needed for the wizard to be editable. They are: storage account, resource group, client id, client secret, tenant id, and subscription id

#224 introduced permissions checker with a placeholder message.

It needs to get proper UX.

cc @terezanovotna

194bd0e Introduced a workaround to do lazy migration of Cost Data. Once the data are migrated by backend, it should be removed.