@electrolux-oss/plugin-infrawallet 0.1.9 → 0.1.10

package/README.md

@@ -28,17 +28,18 @@ infraWallet:
     defaultShowLastXMonths: 3 # 3 by default, or other numbers, we recommend it less than 12
 ```
 
-### Default Settings for Frontend
+#### Customizing the InfraWalletPage Title and Subtitle
 
-Site admins can configure the default view for InfraWallet, including the default group by dimension, and the default
-query period. Add the following configurations to your `app-config.yaml` file if the default view needs to be changed.
+By default, the `InfraWalletPage` component is configured in the `packages/app/src/App.tsx` file as follows:
 
-```yaml
-# note that infraWallet exists at the root level, it is not the same one for backend configurations
-infraWallet:
-  settings:
-    defaultGroupBy: none # none by default, or provider, category, service, tag:<tag_key>
-    defaultShowLastXMonths: 3 # 3 by default, or other numbers, we recommend it less than 12
+```ts
+<Route path="/infrawallet" element={<InfraWalletPage />} />
+```
+
+To customize the title and subtitle of the InfraWalletPage, you can modify the route in the same file as shown below:
+
+```ts
+<Route path="/infrawallet" element={<InfraWalletPage title="Custom title" subTitle="Custom subTitle" />} />
 ```
 
 ### Define Cloud Accounts in app-config.yaml
@@ -111,6 +112,35 @@ backend:
           tableId: <big_query_table_id>
 ```
 
+#### Confluent Cloud
+
+To manage Confluent Cloud costs, you need to create an API key (Service account) for your Organization with the 'Cloud resource management' resource scope, you can find the documentation [here](https://docs.confluent.io/cloud/current/security/authenticate/workload-identities/service-accounts/api-keys/manage-api-keys.html#add-an-api-key). Once you have your API key details, add the following settings to `app-config.yaml`:
+
+```yaml
+backend:
+  infraWallet:
+    integrations:
+      confluent:
+        - name: <unique_name_of_this_account>
+          apiKey: <your_api_key>
+          apiSecret: <your_api_key_secret>
+```
+
+#### Mongo Atlas
+
+To manage Mongo Atlas costs, you need to create an API key for your Organization with the 'Organization Billing Viewer' permission, you can find the documentation [here](https://www.mongodb.com/docs/atlas/configure-api-access/#std-label-about-org-api-keys). Once you have your API key details, add the following settings to `app-config.yaml`:
+
+```yaml
+backend:
+  infraWallet:
+    integrations:
+      mongoatlas:
+        - name: <unique_name_of_this_account>
+          orgId: <id_organization_mongo_atlas>
+          publicKey: <public_key_of_your_api_key>
+          privateKey: <private_key_of_your_api_key>
+```
+
 ### Adjust Category Mappings if Needed
 
 The category mappings are stored in the plugin's database. If there is no mapping found in the DB when initializing the plugin, the default mappings will be used. The default mappings can be found in the [plugins/infrawallet-backend/seeds/init.js](plugins/infrawallet-backend/seeds/init.js) file. You can adjust this seed file to fit your needs, or update the database directly later on.

package/package.json

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