https://github.com/nshttpd/oci-api-keygen

command line tool to create API Keys for OCI tenancies
https://github.com/nshttpd/oci-api-keygen

apikey-manager oci oracle-cloud

Last synced: 5 months ago
JSON representation

command line tool to create API Keys for OCI tenancies

• Host: GitHub
• URL: https://github.com/nshttpd/oci-api-keygen
• Owner: nshttpd
• License: bsd-3-clause
• Created: 2018-01-28T17:32:34.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2018-07-04T16:31:55.000Z (almost 8 years ago)
• Last Synced: 2024-06-20T10:19:02.886Z (almost 2 years ago)
• Topics: apikey-manager, oci, oracle-cloud
• Language: Go
• Size: 867 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
### oci-api-keygen

In order to use the [Oracle Compute Infrastructure](https://cloud.oracle.com/en_US/infrastructure/compute) API a

user must generate a key to upload into the web console. This key is used to authenticate to the API for a specific

[tenancy](https://docs.us-phoenix-1.oraclecloud.com/Content/GSG/Concepts/settinguptenancy.htm) for tools such as 

[Terraform](https://www.terraform.io/) or other third-party or home build tools.

The [instructions for creating](https://docs.us-phoenix-1.oraclecloud.com/Content/API/Concepts/apisigningkey.htm) 

these keys is a multi step process involving openssl and command line while keeping track of the files that are 

generated. This tool handles all of that for you. It'll generate the private and public key along with keeping 

track of the tenancies they are created for and the fingerprints of the keys.

#### Installation

The usual.

`go get -u github.com/nshttpd/oci-api-keygen`

At some point in the future binaries for different platorms will be provided.

#### Usage

The default location for the public and private keys along with a configuration file will be `~/.oci/` where most 

other things associated with OCI are stored. This can be overridden with a `--config` parameter and the keys 

will be stored in the same directory as where the config file is set to.

The basics are :

**Create**

create a set of keys for a tenancy

> oci-api-keygen create [tenancy]

**List**

List all of the tenancies that have had keys generated for them

> oci-api-keygen list

Show fingerprint for a tenancy

> oci-api-keygen list [tenancy]

**Delete**

Delete all the artifacts for a tenancy and remove it from the config file.

> oci-api-keygen delete [tenancy]