-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[WIP][forge] rust bindings for forge indexer/testnet deployer
- Loading branch information
Showing
8 changed files
with
370 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# Forge K8s Deployer Backend | ||
|
||
This backend manages Forge "deployers", which are k8s jobs that spin up the necessary k8s infrastructure for Forge tests to run. | ||
They mostly involve state management of the Forge namespace, ancillary resources like configmaps, and the deployer jobs themselves. | ||
|
||
Forge deployers: | ||
|
||
- Each deploy a single "component" of Forge infra, which may be dependent on some other components or resources. For example, this can be an indexer stack, which in turn relies on a testnet stack to exist | ||
- Can take in customization values via the env var FORGE_DEPLOY_VALUES_JSON | ||
- Have a known values schema but mostly rely on a "profile" that is suitable for most tests, that contains default sane values |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
// Copyright (c) Aptos Foundation | ||
// SPDX-License-Identifier: Apache-2.0 | ||
|
||
pub const FORGE_INDEXER_DEPLOYER_DOCKER_IMAGE_REPO: &str = | ||
"us-docker.pkg.dev/aptos-registry/docker/forge-indexer-deployer"; | ||
pub const FORGE_TESTNET_DEPLOYER_DOCKER_IMAGE_REPO: &str = | ||
"us-docker.pkg.dev/aptos-registry/docker/forge-testnet-deployer"; | ||
|
||
/// The version of the forge deployer image to use. | ||
pub const FORGE_DEPLOYER_IMAGE_TAG: &str = "main"; // default to the latest stable build from the main branch | ||
|
||
/// This is the service account name that the deployer will use to deploy the forge components. It may require extra permissions and additonal setup | ||
pub const FORGE_DEPLOYER_SERVICE_ACCOUNT_NAME: &str = "forge"; | ||
|
||
/// This is the environment variable that is required to be set in the pod to provide the deployer | ||
pub const FORGE_DEPLOYER_VALUES_ENV_VAR_NAME: &str = "FORGE_DEPLOY_VALUES_JSON"; | ||
|
||
pub const DEFAULT_FORGE_DEPLOYER_PROFILE: &str = "large"; |
Oops, something went wrong.