The directory in which you run substrate-bootstrap-management-account
becomes the root of your Substrate repository. This is the directory in which you’re always expected to run Substrate commands because this is the directory where all its various files are stored.
We recommend here, and the tools recommend whenever they create files on your behalf, that all these files be committed to some form of version control. You are free to create a repository specifically for Substrate, to add Substrate to the root of an existing repository, or to add Substrate in a subdirectory of a new or existing repository. If you’re already a Terraform user, we find it convenient for Substrate to be committed to the same repository in which you store existing Terraform modules.
The following index describes the contents and purpose of all the files the various Substrate tools create in your Substrate repository on your behalf.
modules
intranet
lambda-function
peering-connection
substrate
root-modules
admin
deploy
network
substrate.accounts.txt
substrate.admin-networks.json
substrate.default-region
substrate.environments
substrate.intranet-dns-domain-name
substrate.networks.json
substrate.oauth-oidc-client-id
substrate.oauth-oidc-client-secret-timestamp
substrate.okta-hostname
substrate.prefix
substrate.qualities
substrate.regions
substrate.saml-metadata.xml
substrate.valid-environment-quality-pairs.json