This is the backend for the deno.land/x service.
There are a few guidelines / rules that you should follow when publishing a module:
Additionally to these guidelines there are also hard limits:
If you need an increase to these quotas, please reach out to [email protected].
Make sure to follow the official instructions to login to ECR via the Docker cli - this is needed to push the images used by the Lambda deployment to ECR.
aws ecr get-login-password --region region | docker login --username AWS --password-stdin aws_account_id.dkr.ecr.region.amazonaws.com
aws
CLI.aws
by running aws configure
terraform/terraform.tfvars.example
to terraform/terraform.tfvars
terraform/terraform.tfvars
: set mongodb_atlas_org_id
to yourmongodb_atlas_private_key
andmongodb_atlas_public_key
with the API key you created earlier.terraform/
and comment out the backend
section in themeta.tf
file (important for first-time apply)terraform init
terraform plan -var-file terraform.tfvars -out plan.tfplan
terraform apply plan.tfplan
aws s3 ls | grep 'terraform-state' # take note of your tf state bucket name
# before the final step, go back and remove the comments from step 5
terraform init -backend-config "bucket=<your-bucket-name>" -backend-config "region=<aws-region>"
Terraform automatically provisions a MongoDB cluster in a separate project.
production
.modules
.default
indexes/atlas_search_index_mapping.json
by_owner_and_repo
likeindexes/modules_by_owner_and_repo.json
by_is_unlisted_and_star_count
like it is defined inindexes/modules_by_is_unlisted_and_star_count.json
builds
.by_name_and_version
like it is defined inindexes/builds_by_name_and_version.json
Before destroying your staging environment, make sure to:
terraform state pull
to make a local copy of your state filebackend
section of the meta.tf
fileterraform init -backend-config "region=<aws-region>"
You can then run terraform destroy
to completely remove your staging
environment.
To run tests locally, make sure you have Docker and docker-compose installed. Then run:
make test