transip
This library crate can be used for calling functions on the Transip Api
endpoint.
Only part of the api is implemented. The main reason for writing this library is the ability
to CRUD
dns records for a particular domain. This functionality can be used to respond to DNS01 challenges from the Let's Encrypt
servers.
This type of challenge is needed to get wildcard certificates.
Example
use transip::{configuration_from_environment, Client, api::general::GeneralApi};
fn main() {
let mut client = configuration_from_environment()
.and_then(Client::try_from)
.expect("No cliƫnt");
let pong = client.api_test().expect("api test failed");
assert_eq!(pong.as_str(), "pong");
}
Environment variables
The following environment variables should be set!.
TRANSIP_API_USERNAME
This is the username used in authentication
Example
TRANSIP_API_PRIVATE_KEY
This is the name of the file that holds the pem encoded private key used in authentication
Example
TRANSIP_API_READONLY
Can be 'true' or 'false'. If you wan't to prevent accidental modifications set this to 'true'.
Example
TRANSIP_API_WHITELISTED_ONLY
Can be 'true' or 'false'. If you wan't to access the api on a whitelisted ipaddress set this to 'true'.
TRANSIP_API_TOKEN_EXPIRATION
Authentication means receiving a token. The interval in which the received will expired can be controlled.
Example 1
Example 2
Example 3
TRANSIP_API_LOG_DIR
Directory where the rotating log files are written.
Example
TRANSIP_API_TOKEN_PATH
Name of the file where the authentication token received from the endpoint will be written to.
Example