You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS CodeBuild projects support caching of dependencies for a build. This allows a user to specify an S3 bucket and a path within that bucket that will be used as cache storage for paths specified in a section of the buildspec YAML file.
I've seen this introduced in this blog post, where it is shown how to configure a CodeBuild project with caching from the AWS dashboard. The example use case is about Maven dependencies, which is close to my team's use case, albeit for Gradle instead. Using caching would help speed up our build significantly and since we are using terraform to manage our pipeline, it would be great to be able to do it from there.
Expected Behavior
It would be helpful if theaws_codebuild_project resource supported cache configuration. Maybe something along the lines of:
resource"aws_codebuild_project""foobar" {
[...]
cache {
# s3 is the only option at the moment other than no cache at all, # but there's a dropdown for it, so it might expandtype="s3"location="some-bucket"path_prefix="/some/path"
}
[...]
}
Factoids
From the dashboard, it seems that it's only possible to add cache from a newly created project, but not adding it to an existing one when editing. However, boto3 seems to support configuring cache when calling update_project in an existing project, so I guess it should be possible programatically somehow. I'm not familiar with how this is implemented in Terraform as I didn't have time to look at the source yet.
The text was updated successfully, but these errors were encountered:
This issue has been automatically migrated to hashicorp/terraform-provider-aws#2842 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
AWS CodeBuild projects support caching of dependencies for a build. This allows a user to specify an S3 bucket and a path within that bucket that will be used as cache storage for paths specified in a section of the buildspec YAML file.
I've seen this introduced in this blog post, where it is shown how to configure a CodeBuild project with caching from the AWS dashboard. The example use case is about Maven dependencies, which is close to my team's use case, albeit for Gradle instead. Using caching would help speed up our build significantly and since we are using terraform to manage our pipeline, it would be great to be able to do it from there.
Expected Behavior
It would be helpful if the
aws_codebuild_project
resource supported cache configuration. Maybe something along the lines of:Factoids
From the dashboard, it seems that it's only possible to add cache from a newly created project, but not adding it to an existing one when editing. However, boto3 seems to support configuring cache when calling
update_project
in an existing project, so I guess it should be possible programatically somehow. I'm not familiar with how this is implemented in Terraform as I didn't have time to look at the source yet.The text was updated successfully, but these errors were encountered: