Module sandbox_setup_inputs 

The facts an AWS sandbox’s setup renders its scaffolding from. Setup applies them and the runtime never re-reads them, so a change to any of them needs setup to run again.

Structs

SetupAccount

The account a sandbox’s scaffolding is rendered into.

Constants

SETUP_INPUTS_COMPARISON_ACCOUNT

For comparing two stacks without an account. The region stays the token so a {region} host and a literal region never render the same ARN.

Functions

aws_sandbox_build_role

The build role setup renders for this sandbox. With renders_bundle it only pulls the image the rendered bundle names; otherwise it reads bundle_uri.

aws_sandbox_egress_network_id

The id of the setup-owned network every AWS sandbox connector attaches to. The error is the refusal message, for the caller to wrap in its own error.

aws_sandbox_entry_renders_bundle

aws_sandbox_renders_bundle for the sandbox’s own entry.

aws_sandbox_remote_grant

The Remote Bindings grant setup renders for this sandbox, None when it publishes none.

aws_sandbox_renders_bundle

Whether the controller renders this sandbox’s bundle into the deployment’s bundle Storage, SANDBOX_BUNDLE_STORAGE_ID: the sandbox depends on it. Setup adds the Storage for a Live sandbox released as a container image; a deployment set up before it existed builds from the bundle a publisher wrote into the store its setup granted.

aws_sandbox_setup_inputs

Each setup input with the name a refused update reports it by. A new bundle under the same stable prefix, or a new tag in the same private repository, leaves them unchanged. For a Live sandbox the bundle’s store and the base image’s repository name are not inputs at all: they are fixed by the setup that granted them. The repository’s namespace is.

comparable_aws_sandbox_setup_inputs

aws_sandbox_setup_inputs for comparing stacks, which cannot fail: a sandbox whose inputs do not resolve counts as its whole configuration, so any change to it needs setup.