Expose elastic_concurrent_builds on resource config #261
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LukeSheard
force-pushed
the
01-23-expose_elastic_concurrency_enabled_on_resource_config
branch
from
2d7cef4 to
2db2c0b
Compare
dglsparsons
reviewed
Jan 23, 2025
Comment on lines
+1017
to
+1019
| if !r.ElasticConcurrencyEnabled.IsNull() { | ||
| resourceConfig.ElasticConcurrencyEnabled = r.ElasticConcurrencyEnabled.ValueBool() | ||
| } |
There was a problem hiding this comment.
Can you add tests to demonstrate that it works? 😂
There was a problem hiding this comment.
Yup, once I've validated it locally ✌️
LukeSheard
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enable the new elastic concurrency property on project settings through the terraform provider.