#office-hours - March 2021

Hashicorp Kubernetes Provider - is it ready for prime-time yet? Targeting mainstream cloud platforms and managed k8s, is anyone inclined to share their best practices (e.g. multiple states “Infra” vs “Service deployments”, integration into CICD, etc)?

decrypt-user-password:
	@if [[ "$(USER)" == "" ]]; then \
		echo "Please set USER to first_name.last_name prior to running 'make decrypt-user-password'" && exit 1; \
	fi;
	@PGP_KEY_JSON=$$(aws secretsmanager get-secret-value --secret-id terraform_iam_users_pgp_key | jq -r ".SecretString"); \
		export GPG_TTY=$(tty); \
		echo $$PGP_KEY_JSON | jq -r ".terraform_users_pgp_private_key" | gpg --import; \
		export PGP_PASSPHRASE=$$(echo $$PGP_KEY_JSON | jq -r ".terraform_users_pgp_passphrase"); \
		cd ./components/iam_infra; \
		export ENCRYPTED_PASSWORD=$$(terraform output --json | jq -r '.user_encrypted_passwords.value | .["$(USER)"]'); \
		export RAW_PASSWORD=$$(echo $$ENCRYPTED_PASSWORD | base64 --decode | gpg --decrypt --batch --passphrase $$PGP_PASSPHRASE); \
		printf "\nPrivate message $(USER) in Slack with the following:\n\n"; \
		echo "Hey, you got a fancy new AWS Login :cool-doge: Check out the info and guide below to get everything setup:"; \
		echo ""; \
		echo "AWS Account Setup Guide: REDACTED"; \
		echo "Console Login URL: REDACTED"; \
		echo "username: $(USER)"; \
		echo "password: $$RAW_PASSWORD";

When private DNS is enabled, you’re able to access your API via private or public DNS. (This setting doesn’t affect who can access your API, only which DNS addresses they can use.) However, you cannot access public APIs from a VPC by using an API Gateway VPC endpoint with private DNS enabled. Note that these DNS settings don’t affect the ability to call these public APIs from the VPC if you’re using an edge-optimized custom domain name to access the public API. Using an edge-optimized custom domain name to access your public API (while using private DNS to access your private API) is one way to access both public and private APIs from a VPC where the endpoint has been created with private DNS enabled.

> For anyone following this ticket, PSPs will be deprecated in 1.21 with removal targeted for 1.25.

This is correct. We moved deprecation from 1.22 to 1.21 because we know that existing PSP API will not be losslessly backward compatible with a future replacement. PSP removal is staying at the previously planned 1.25.

gcloud alpha resource-config bulk-export --project my-project --resource-format=terraform