Struct DeploymentInventoryService 

pub struct DeploymentInventoryService {
    pub ansible_runner: AnsibleRunner,
    pub ansible_provisioner: AnsibleProvisioner,
    pub cloud_provider: CloudProvider,
    pub inventory_file_path: PathBuf,
    pub s3_repository: S3Repository,
    pub ssh_client: SshClient,
    pub terraform_runner: TerraformRunner,
    pub working_directory_path: PathBuf,
}

Fields

ansible_runner: AnsibleRunner

ansible_provisioner: AnsibleProvisioner

cloud_provider: CloudProvider

inventory_file_path: PathBuf

s3_repository: S3Repository

ssh_client: SshClient

terraform_runner: TerraformRunner

working_directory_path: PathBuf

Implementations

impl DeploymentInventoryService

pub async fn generate_or_retrieve_inventory( &self, name: &str, force: bool, binary_option: Option<BinaryOption>, ) -> Result<DeploymentInventory>

Generate or retrieve the inventory for the deployment.

If we’re creating a new environment and there is no inventory yet, a empty inventory will be returned; otherwise the inventory will represent what is deployed currently.

The force flag is used when the deploy command runs, to make sure that a new inventory is generated, because it’s possible that an old one with the same environment name has been cached.

The binary option will only be present on the first generation of the inventory, when the testnet is initially deployed. On any subsequent runs, we don’t have access to the initial launch arguments. This means any branch specification is lost. In this case, we’ll just retrieve the version numbers from the genesis node in the node registry. Most of the time it is the version numbers that will be of interest.

pub fn setup_environment_inventory(&self, name: &str) -> Result<()>

Create all the environment inventory files. This also updates the SSH client to route the private nodes the NAT gateway if it exists.

This is used when ‘generate_or_retrieve_inventory’ is not used, but you still need to set up the inventory files.

pub async fn upload_network_contacts( &self, inventory: &DeploymentInventory, contacts_file_name: Option<String>, ) -> Result<()>

pub async fn generate_or_retrieve_client_inventory( &self, name: &str, region: &str, force: bool, binary_option: Option<BinaryOption>, ) -> Result<ClientsDeploymentInventory>

Generate or retrieve the Client inventory for the deployment.

If we’re creating a new environment and there is no inventory yet, an empty inventory will be returned; otherwise the inventory will represent what is deployed currently.

The force flag is used when the deploy command runs, to make sure that a new inventory is generated, because it’s possible that an old one with the same environment name has been cached.

Trait Implementations

impl From<&ClientsDeployer> for DeploymentInventoryService

fn from(item: &ClientsDeployer) -> Self

Converts to this type from the input type.

impl From<&TestnetDeployer> for DeploymentInventoryService

fn from(item: &TestnetDeployer) -> Self

Converts to this type from the input type.