Oracle Cloud Infrastructure (OCI)
Local Komiser CLI (Single Account)
Komiser now supports multiple cloud accounts by default. Account configuration is done through the config.toml file, using the CREDENTIALS_FILE
method.
We’ve also added 2 methods of persisting your account data.
Data persistence
Choose between these two methods of persisting your OCI account data.
Postgres
Add to config.toml file
postgres
and a database komiser
on the local Postgres server. SQLite
Configuration file
In the configuration file you add the OCI account name, authentication method (CREDENTIALS_FILE) and a data persistence.
Credentials file
Use an OCI user and an API key for authentication. In this case, you’ll need to put your tenancy OCID, user OCID, region name, the path to an API key, and the fingerprint of the API key.
Download OCI CLI, find instructions here
The easiest way is to let OCI walk you through the setup process by executing the following command:
Now, a config file and key pair have been created in your local .oci
folder:
Since Komiser looks for credentials in a file called credentials
. Create a credentials
file in the .oci
folder and copy the contents of the config
file to it.
Contents of credentials file
Make sure that the path added in the
config.toml
is correct to ensure that Komiser has access to the credentials file.
Run it!
That should be it. Try out the following command from your command prompt to start the server:
If you point your browser to http://localhost:3000
, you should be able to see your OCI resources.
Local Komiser CLI (Multiple accounts)
Simply add more authentication blocks to the configuration file
Contents of credentials file
Run it!
That should be it. Try out the following command from your command prompt to start the server:
If you point your browser to http://localhost:3000
, you should be able to see your OCI resources.