microvms-app 0.12.0

The MicroVMs client's use cases, written against ports: the control plane, sandboxes, sessions, agents
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

// SPDX-License-Identifier: Apache-2.0
//! The two calls outside the MicroVMs API that `ensure_image` makes: the caller's account,
//! for the image ARN, and the artifact upload (#221, IMAGE-8).
//!
//! [`BuildServices`] is the port. `Sandbox::with_build_services` takes one, a test records
//! the calls and answers them, and production gets `SignedBuildServices` (in
//! `microvms-edges`, re-exported as `microvms_core::control::SignedBuildServices`) through the
//! plane's adapters on the first `ensure_image`. The account comes from STS because
//! `GetMicrovmImage` takes an ARN and the service rejects a bare name; `GetCallerIdentity`
//! answers the account for any identity and needs no permission to make.

use futures_util::future::BoxFuture;

use crate::error::Error;

/// The seam `ensure_image` reaches STS and S3 through.
pub trait BuildServices: Send + Sync {
    /// The caller's twelve-digit account id.
    fn caller_account(&self) -> BoxFuture<'_, Result<String, Error>>;

    /// Puts `bytes` at `s3://<bucket>/<key>`.
    fn put_object<'a>(
        &'a self,
        bucket: &'a str,
        key: &'a str,
        bytes: Vec<u8>,
    ) -> BoxFuture<'a, Result<(), Error>>;
}