OpenStax.Keystone v0.1.8 OpenStax.Keystone View Source
OpenStax Keystone provides bindings for OpenStack Identity v2.0 API for the Elixir programming language.
It is currently capable of periodically retreiving token from the endpoint.
It supports adding multiple endpoints in the runtime, but if you want you may add only one during startup.
Installation
Add the following tuple to deps
in your mix.exs
:
{:openstax_keystone, "~> 0.1"}
and :openstax_keystone
to your app_list
.
Examples
If you use username/password authentication, and Tenant ID as your identifier, use the following code in order to add the new keystone endpoint:
OpenStax.Keystone.Endpoint.register_password(:my_storage, :"2.0", "https://auth.example.com/v2.0", "my_tenant_id", nil, "john", "secret")
If you use username/password authentication, and Tenant Name as your identifier, use the following code in order to add the new keystone endpoint:
OpenStax.Keystone.Endpoint.register_password(:my_storage, :"2.0", "https://auth.example.com/v2.0", nil, "my_tenant_name", "john", "secret")
If you use token authentication, and Tenant ID as your identifier, use the following code in order to add the new keystone endpoint:
OpenStax.Keystone.Endpoint.register_token(:my_storage, :"2.0", "https://auth.example.com/v2.0", "my_tenant_id", nil, "secrettoken")
If you use token authentication, and Tenant Name as your identifier, use the following code in order to add the new keystone endpoint:
OpenStax.Keystone.Endpoint.register_token(:my_storage, :"2.0", "https://auth.example.com/v2.0", nil, "my_tenant_name", "secrettoken")
Link to this section Summary
Link to this section Functions
Called when an application is started.
This function is called when an application is started using
Application.start/2
(and functions on top of that, such as
Application.ensure_started/2
). This function should start the top-level
process of the application (which should be the top supervisor of the
application’s supervision tree if the application follows the OTP design
principles around supervision).
start_type
defines how the application is started:
:normal
- used if the startup is a normal startup or if the application is distributed and is started on the current node because of a failover from another node and the application specification key:start_phases
is:undefined
.{:takeover, node}
- used if the application is distributed and is started on the current node because of a failover on the nodenode
.{:failover, node}
- used if the application is distributed and is started on the current node because of a failover on nodenode
, and the application specification key:start_phases
is not:undefined
.
start_args
are the arguments passed to the application in the :mod
specification key (e.g., mod: {MyApp, [:my_args]}
).
This function should either return {:ok, pid}
or {:ok, pid, state}
if
startup is successful. pid
should be the PID of the top supervisor. state
can be an arbitrary term, and if omitted will default to []
; if the
application is later stopped, state
is passed to the stop/1
callback (see
the documentation for the c:stop/1
callback for more information).
use Application
provides no default implementation for the start/2
callback.
Callback implementation for Application.start/2
.