Troubleshooting
Last updated
Last updated
Duplicate Resource Name
You may have configured your output with a static name, such that multiple users will result in a resource with the same resource name.
-> Configure a dynamic resource name using string interpolation. Examples can be seen in
The resource may be defined in a different terraform file. This commonly happens when people are testing multiple starter kits. You can fix this by renaming one of the resources.
Bad Grant Kit Name
Grant kit names must start with a letter or underscore, and may contain only letters, digits, underscores, and dashes.
Grant Kit Already Exists
Names must be unique across all of your grant kits.
Abbey Identity Not Found
Your Abbey Identity is the email you used to sign up for Abbey including the domain. Check that the email specified is the same as that value.
API Error
Please contact us for further support. You can find us on our Slack.
Request Denied Due to Unable to add Approver Check
This may happen if you have not granted the Abbey GitHub App the correct permissions. Check that there isn't a permissions request at Settings -> GitHub Apps -> Abbey Labs
Request Denied Due to Failing Check
This can happen when the output of your grant kit has issues when trying to run terraform plan. Inspect the error log in the GitHub actions run for your PR for details.
ABBEY_TOKEN or another API Token is missing from your GitHub Secrets.
-> See the Quickstart for instructions.
GitHub may not have permissions to write to PRs.
You are missing a Connection to GitHub or that connection is missing access permissions to your repo.
-> See Connect a Repofor instructions.
Error refreshing state: HTTP remote state endpoint requires auth
Double check that your Abbey API token is not expired! If it's expired, you'll need to create a new one.
Please make sure that the Materialize GitHub Action has succeeded. To check this, go to your repository containing the grant kit and click on Actions -> Abbey Grant Kit Materialize. If the Action has failed, inspect the log for further debugging.
Common causes of failure are:
Your terraform file is misconfigured. Some possible causes and solutions are listed in Common Issues
A request may fail for many reasons. Some common reasons are:
You have misspelled the name of the organization or repo when defining the output location. -> Check that you have correctly specified your repo correctly.
You are missing a Connection to GitHub for the repo where you want to store access.tf.
-> See Connect a Repo for instructions above for how to create a Connection.
Please make sure that the Generate Policy Input GitHub Action has succeeded. To check this, go to your repository containing the grant kit and click on Actions -> Abbey Grant Kit Generate Policy Input. If the Action has failed, inspect the log for further debugging. See Common Issuesfor examples of failures and their solutions.
Common reasons to have a failing policy
The policy must be in the same repo as your output. Check to make sure that this is the case.
Policy is incorrectly defined. See Policiesfor how to configure a policy.
Please make sure that the Generate Policy Input GitHub Action has succeeded. If this Policy Fails, the request will be denied. To check this, go to your repository containing the grant kit and click on Actions -> Abbey Grant Kit Generate Policy Input. If the Action has failed, inspect the log for further debugging. See Common Issuesfor examples of failures and their solutions.
-> See for instructions.
