/*
* 3DS OUTSCALE API
*
* Welcome to the OUTSCALE API documentation.<br /> The OUTSCALE API enables you to manage your resources in the OUTSCALE Cloud. This documentation describes the different actions available along with code examples.<br /><br /> Throttling: To protect against overloads, the number of identical requests allowed in a given time period is limited.<br /> Brute force: To protect against brute force attacks, the number of failed authentication attempts in a given time period is limited.<br /><br /> Note that the OUTSCALE Cloud is compatible with Amazon Web Services (AWS) APIs, but there are [differences in resource names](https://docs.outscale.com/en/userguide/About-the-APIs.html) between AWS and the OUTSCALE API.<br /> You can also manage your resources using the [Cockpit](https://docs.outscale.com/en/userguide/About-Cockpit.html) web interface.<br /><br /> An OpenAPI description of this API is also available for download: <button>[GitHub repository](https://github.com/outscale/osc-api)</button><br /> # Authentication Schemes ### Access Key/Secret Key The main way to authenticate your requests to the OUTSCALE API is to use an access key and a secret key.<br /> The mechanism behind this is based on AWS Signature Version 4, whose technical implementation details are described in [Signature of API Requests](https://docs.outscale.com/en/userguide/Signature-of-API-Requests.html).<br /><br /> In practice, the way to specify your access key and secret key depends on the tool or SDK you want to use to interact with the API.<br /> > For example, if you use OSC CLI: > 1. You need to create an **~/.osc/config.json** file to specify your access key, secret key, and the Region of your account. > 2. You then specify the `--profile` option when executing OSC CLI commands. > > For more information, see [Installing and Configuring OSC CLI](https://docs.outscale.com/en/userguide/Installing-and-Configuring-OSC-CLI.html). See the code samples in each section of this documentation for specific examples in different programming languages.<br /> For more information about access keys, see [About Access Keys](https://docs.outscale.com/en/userguide/About-Access-Keys.html). > If you try to sign requests with an invalid access key four times in a row, further authentication attempts will be prevented for 1 minute. This lockout time increases 1 minute every four failed attempts, for up to 10 minutes. ### Login/Password For certain API actions, you can also use basic authentication with the login (email address) and password of your TINA account.<br /> This is useful only in special circumstances, for example if you do not know your access key/secret key and want to retrieve them programmatically.<br /> In most cases, however, you can use the Cockpit web interface to retrieve them.<br /> > For example, if you use OSC CLI: > 1. You need to create an **~/.osc/config.json** file to specify the Region of your account, but you leave the access key value and secret key value empty (`""`). > 2. You then specify the `--profile`, `--authentication-method`, `--login`, and `--password` options when executing OSC CLI commands. See the code samples in each section of this documentation for specific examples in different programming languages. > If you try to sign requests with an invalid password four times in a row, further authentication attempts will be prevented for 1 minute. This lockout time increases 1 minute every four failed attempts, for up to 10 minutes. ### No Authentication A few API actions do not require any authentication. They are indicated as such in this documentation.<br /> ### Other Security Mechanisms In parallel with the authentication schemes, you can add other security mechanisms to your OUTSCALE account, for example to restrict API requests by IP or other criteria.<br /> For more information, see [Managing Your API Accesses](https://docs.outscale.com/en/userguide/Managing-Your-API-Accesses.html). # Pagination Tutorial You can learn more about the pagination methods for read calls in the dedicated [pagination tutorial](https://docs.outscale.com/en/userguide/Tutorial-Paginating-an-API-Request.html). # Error Codes Reference You can learn more about errors returned by the API in the dedicated [errors page](api-errors.html).
*
* The version of the OpenAPI document: 1.36.3
* Contact: support@outscale.com
* Generated by: https://openapi-generator.tech
*/
#[derive(Clone, Debug, PartialEq, Default, Serialize, Deserialize)]
pub struct CreateAccountRequest {
/// One or more additional email addresses for the account. These addresses are used for notifications only. If you already have a list of additional emails registered, you cannot add to it, only replace it. To remove all registered additional emails, specify an empty list.
#[serde(rename = "AdditionalEmails", skip_serializing_if = "Option::is_none")]
pub additional_emails: Option<Vec<String>>,
/// The city of the account owner.
#[serde(rename = "City")]
pub city: String,
/// The name of the company for the account.
#[serde(rename = "CompanyName")]
pub company_name: String,
/// The country of the account owner.
#[serde(rename = "Country")]
pub country: String,
/// The ID of the customer. It must be 8 digits.
#[serde(rename = "CustomerId")]
pub customer_id: String,
/// If true, checks whether you have the required permissions to perform the action.
#[serde(rename = "DryRun", skip_serializing_if = "Option::is_none")]
pub dry_run: Option<bool>,
/// The main email address for the account. This address is used for your credentials and notifications.
#[serde(rename = "Email")]
pub email: String,
/// The first name of the account owner.
#[serde(rename = "FirstName")]
pub first_name: String,
/// The job title of the account owner.
#[serde(rename = "JobTitle", skip_serializing_if = "Option::is_none")]
pub job_title: Option<String>,
/// The last name of the account owner.
#[serde(rename = "LastName")]
pub last_name: String,
/// The mobile phone number of the account owner.
#[serde(rename = "MobileNumber", skip_serializing_if = "Option::is_none")]
pub mobile_number: Option<String>,
/// The landline phone number of the account owner.
#[serde(rename = "PhoneNumber", skip_serializing_if = "Option::is_none")]
pub phone_number: Option<String>,
/// The state/province of the account.
#[serde(rename = "StateProvince", skip_serializing_if = "Option::is_none")]
pub state_province: Option<String>,
/// The value added tax (VAT) number for the account.
#[serde(rename = "VatNumber", skip_serializing_if = "Option::is_none")]
pub vat_number: Option<String>,
/// The ZIP code of the city.
#[serde(rename = "ZipCode")]
pub zip_code: String,
}
impl CreateAccountRequest {
pub fn new(
city: String,
company_name: String,
country: String,
customer_id: String,
email: String,
first_name: String,
last_name: String,
zip_code: String,
) -> CreateAccountRequest {
CreateAccountRequest {
additional_emails: None,
city,
company_name,
country,
customer_id,
dry_run: None,
email,
first_name,
job_title: None,
last_name,
mobile_number: None,
phone_number: None,
state_province: None,
vat_number: None,
zip_code,
}
}
}