This repository has been archived by the owner on Dec 24, 2024. It is now read-only.
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Terraform driven eks deploy alternative providers (#123)
* new: provision standalone eks cluster using terraform only Create custom 'brokerpak-eks-terraform-provision' module using eks-brokerpak as source; specify custom parameters to provision with * update: terraform and modules * new: add bind resource for eks-terraform cluster Create user-provided service based on binding to pass to solrcloud broker * fix/refactor: bind depends on provision * update/fix: child modules can't specify their own provider blocks Reference: GSA-TTS/datagov-brokerpak-eks#79 * cleanup: remove unreferenced variable * new: add eks_terraform params for staging/prod * fix: ensure bind actually waits for cluster_functional Explicit output from module to module * new: install aws/kubectl/helm tools for terraform apply * fix: don't mess up ubuntu's path * test: attempt to fix github action path Trying to determine where home is and where the real path actually is * test: ensure that the aws-iam-authenticator was installed Also tests whether the command is available later in the same job * test: the command actually wasn't added to the path yet.. Reference: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path * fix: high hopesgit add . aws-iam-authenticator needs AWS Credentials in the env * new: successfully configure providers for eks as a submodule * revert: no need to set AWS creds The S3 Backend is set up properly alongside terraform AWS credentials, so this broke that * update: supply the module's required_provider using the correct alias * fix: provide AWS creds for the module to use with kubernetes provider The module needs AWS creds so the kubernetes provider can use aws-iam-authenticator when it connects. * workaround: temporarily comment out the resources that aren't working We have yet to resolve the issue with the kubernetes_provider in the bind module not working, due to it having a dependency on another module. * refactor: move declaration of IaaS-only resources to the managed-boundary Technically this is where they belong, in terms of our SSP and diagram terminology. Note also that we are no longer invoking the submodules separately, but rather directly invoking the parent module at `datagov-brokerpak-eks/terraform` * lint: fix terraform fmt * fix: uncomment CF-side resources * fix: name "credentials" is implicit * update: eks-brokerpak no longer needs a branch Dual support for brokerpak mode or terraform module mode is enabled :) * fix: terraform string literals don't like newlines Reference: hashicorp/terraform-provider-vault#307 * fix: use data sources for space/org lookup * fix: set variables based on service name update VCAP_SERVICE selection to use the correct service based on service name, not service type * new: install tools as TERRAFORM_PRE_RUN Since dflook action is a separate container, the tools need to be pulled in properly. The terraform working directory becomes part of the path for that step, so installing the tools there works :) * lint: ran terraform fmt * new: add tools to known path After lots of tries, this seems to be the most reliable method * temp: work off of branch until it gets merged Too many changes to keep track off.. the branch is fully functional for terraform only stuff, but brokerpak stuff is a bit broken :/ Co-authored-by: Bret Mogilefsky <[email protected]>
- Loading branch information