这是indexloc提供的服务,不要输入任何密码
Skip to content

Expose elastic_concurrent_builds on resource config #261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

LukeSheard
Copy link
Contributor

Enable the new elastic concurrency property on project settings through the terraform provider.

@LukeSheard LukeSheard force-pushed the 01-23-expose_elastic_concurrency_enabled_on_resource_config branch from 2d7cef4 to 2db2c0b Compare January 23, 2025 11:13
Comment on lines +1017 to +1019
if !r.ElasticConcurrencyEnabled.IsNull() {
resourceConfig.ElasticConcurrencyEnabled = r.ElasticConcurrencyEnabled.ValueBool()
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add tests to demonstrate that it works? 😂

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, once I've validated it locally ✌️

@LukeSheard LukeSheard changed the title Expose elastic_concurrency_enabled on resource config Expose elastic_concurrent_builds on resource config Jan 23, 2025
@apidhoro
Copy link

Hi! Are these changes related to https://vercel.com/changelog/enterprise-teams-can-now-ship-faster-without-build-queues ?

@dglsparsons dglsparsons closed this May 1, 2025
@dglsparsons
Copy link
Collaborator

Hi! Are these changes related to https://vercel.com/changelog/enterprise-teams-can-now-ship-faster-without-build-queues ?

@apidhoro yes they are :)

@dglsparsons
Copy link
Collaborator

Replaced by #309

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants