update the roadmap status and bump the version (#35)

* update the roadmap status and bump the version

Signed-off-by: Long Zhang <long.zhang@electrolux.com>

* update the readme regarding supporting new cloud vendors

Signed-off-by: Long Zhang <long.zhang@electrolux.com>

---------

Signed-off-by: Long Zhang <long.zhang@electrolux.com>

README.md

@@ -267,13 +267,13 @@ For example, here is a report returned from InfraWallet backend:
 
 The aggregation is done by the frontend after getting all the needed cost reports. This means that as long as the backend returns more cost reports in the same format, InfraWallet can always aggregate and visualize the costs.
 
-When adding a new cloud vendor, you need to implement a client based on the interface [InfraWalletApi](plugins/infrawallet-backend/src/service/InfraWalletApi.ts). Check [AwsClient.ts](plugins/infrawallet-backend/src/service/AwsClient.ts) and [AzureClient.ts](plugins/infrawallet-backend/src/service/AzureClient.ts) as examples.
+When adding a new cloud vendor, you need to implement a client based on the abstract class [InfraWalletClient](plugins/infrawallet-backend/src/service/InfraWalletClient.ts). Check [AwsClient.ts](plugins/infrawallet-backend/src/service/AwsClient.ts) and [AzureClient.ts](plugins/infrawallet-backend/src/service/AzureClient.ts) as examples.
 
 ## Roadmap
 
 - [x] Make IAM user optional for AWS credentials
 - [x] Support Google Cloud Costs
-- [ ] Support filters besides grouping bys
+- [x] Support filters besides grouping bys
 - [ ] WebUI for managing category mappings
 - [ ] Enable users to select a subset of configured cloud accounts as a wallet
 - [ ] Support different currencies

package.json

@@ -1,6 +1,6 @@
 {
   "name": "root",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "private": true,
   "engines": {
     "node": "18 || 20"

plugins/infrawallet-backend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@electrolux-oss/plugin-infrawallet-backend",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "backstage": {
     "role": "backend-plugin"
   },

plugins/infrawallet/README.md

@@ -262,13 +262,13 @@ For example, here is a report returned from InfraWallet backend:
 
 The aggregation is done by the frontend after getting all the needed cost reports. This means that as long as the backend returns more cost reports in the same format, InfraWallet can always aggregate and visualize the costs.
 
-When adding a new cloud vendor, you need to implement a client based on the interface [InfraWalletApi](plugins/infrawallet-backend/src/service/InfraWalletApi.ts). Check [AwsClient.ts](plugins/infrawallet-backend/src/service/AwsClient.ts) and [AzureClient.ts](plugins/infrawallet-backend/src/service/AzureClient.ts) as examples.
+When adding a new cloud vendor, you need to implement a client based on the abstract class [InfraWalletClient](../infrawallet-backend/src/service/InfraWalletClient.ts). Check [AwsClient.ts](../infrawallet-backend/src/service/AwsClient.ts) and [AzureClient.ts](../infrawallet-backend/src/service/AzureClient.ts) as examples.
 
 ## Roadmap
 
 - [x] Make IAM user optional for AWS credentials
 - [x] Support Google Cloud Costs
-- [ ] Support filters besides grouping bys
+- [x] Support filters besides grouping bys
 - [ ] WebUI for managing category mappings
 - [ ] Enable users to select a subset of configured cloud accounts as a wallet
 - [ ] Support different currencies

plugins/infrawallet/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@electrolux-oss/plugin-infrawallet",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "backstage": {
     "role": "frontend-plugin"
   },