substrate-apigateway-authorizer, substrate-credential-factory, and substrate-instance-factory into substrate-intranet. This is a no-op listed here for transparency. It’s a prerequisite step towards unifying all the Substrate tools as subcommands of substrate, thereby reducing the size and complexity of the Substrate distribution.archive and external Terraform providers by embedding substrate-intranet.zip directly in substrate-create-admin-account. Dependence on these providers will be made optional in a subsequent release.substrate-assume-role (which will have changed if invoked with SUBSTRATE_ROOT set) before forking and executing a child process.substrate-whoami to make it easy to learn the domain, environment, and quality of the AWS account your current credentials operate on.-format=json to substrate-accounts to make it easier to enumerate and act programatically on every AWS account in your organization. See enumerating all your AWS accounts for an example.After upgrading Substrate:
substrate-bootstrap-management-account to grant substrate-whoami the permissions it needs.substrate-bootstrap-network-account to remove coarse-grained organization-wide VPC sharing.substrate-create-admin-account to upgrade your Intranet./accounts page now opens the AWS Console in new browser tabs as it probably always should have.archive, aws, and external providers rather than all of versions.tf. This opens the door to Substrate users adding (and version constraining) additional providers. See additional Terraform providers for an example.aws provider >= 3.49.0.Manager and SubstrateVersion using the default_tags facility of the AWS provider. If you encounter the following error, remove Manager and SubstrateVersion (if present) from the indicated resources and re-run.Error: "tags" are identical to those in the "default_tags" configuration block of the provider: please de-duplicate and try again
SUBSTRATE_ROOT environment variable, if set, rather than always proceeding in whatever the working directory was when invoked.You must upgrade to Terraform 1.0.2 in order to use Substrate 2021.07. Terraform 1.0.2 may be found here:
After upgrading Terraform and Substrate:
substrate-bootstrap-network-account and substrate-bootstrap-deploy-account to complete the Terraform 1.0.2 upgrade there. Note well that tags and tags_all output will be somewhat confusing but will ultimately do the right thing.substrate-create-admin-account and substrate-create-account to complete the Terraform 1.0.2 upgrade for each of your admin and service accounts. Here, too, note well that tags and tags_all output will be somewhat confusing but will ultimately do the right thing.substrate-apigateway-authenticator and substrate-apigateway-index into substrate-intranet. This is a no-op listed here for transparency.>= version constraints on providers (but not Terraform itself).You must upgrade to Terraform 0.15.5 in order to use Substrate 2021.06. Terraform 0.15.5 may be found here:
After upgrading Terraform and Substrate:
substrate-bootstrap-network-account and substrate-bootstrap-deploy-account to complete the Terraform 0.15.5 upgrade there.substrate-create-admin-account -quality="..." to update your Intranet.substrate-create-account -domain="..." -environment="..." -quality="..." for all your service accounts to tag your shared VPCs.If you’ve added any stub provider blocks to your modules, leave them in place for now and accept the deprecation warning. Terraform only allows one required_providers block and that is now managed by Substrate. A future release will accommodate these additional providers.
After upgrading:
substrate-bootstrap-network-account to fix S3 routes.substrate-create-admin-account -quality="..." to enable direct CloudWatch access and make Instance Factory improvements./accounts to the Intranet with links to assume the Administrator and Auditor roles in all your accounts in the AWS Console.-console to substrate-assume-role which attempts to open the AWS Console’s role switching screen in your web browser with all the values filled in.substrate-create-terraform-module which creates the directory structure (with the global and regional pattern), providers, and Substrate metadata for a new Terraform module.After upgrading, run substrate-create-admin-account -quality="..." to add /accounts to your Intranet.
substrate-bootstrap-network-account now creates peering connections between all VPCs in all regions for each environment across all valid qualities.Administrator role in admin accounts that prevented Instance Factory instances from seamlessly assuming the role.You must upgrade to Terraform 0.14.7 in order to use Substrate 2021.03. Terraform 0.14.7 may be found here:
After upgrading:
rm -f -r root-modules/network/*/peering and remove these files from version control.substrate-bootstrap-network-account to peer all your VPCs that should be peered.substrate-create-admin-account -quality="..." to fix Instance Factory IAM roles, following the GSuite SAML setup guide if GSuite is your IdP to also get 12-hour AWS Console sessions.-format from substrate-credentials to substrate-assume-role per request from a customer. Now credentials can be had with or without the export prefix or as JSON a la aws sts assume-role itself.root-modules/admin/*’s awkward dependency on finding GOBIN in the environment. The generated Makefile in each root module remains, however.substrate-assume-role and substrate-credentials now (better) tolerate being invoked from subdirectories of your Substrate repository.aws.network provider was incorrectly added to global modules and thus should have been expected in module stanzas.export AWS_ACCESS_KEY_ID=... line when substrate-assume-role is given a command to execute directly.intranet/regional module to facilitate adding more resources to these APIs.You must upgrade to Terraform 0.13.6 in order to use Substrate 2021.02. Terraform 0.13.6 may be found here:
Contact hello@src-bin.com for prior release notes.