Support max_use and max_lifetime backend parameters
#1568
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.
Change summary
This draft PR adds new
--max-useand--max-lifetimeparameters tofastly backend createandfastly backend update, which can be used to specify themax_useandmax_lifetimebackend fields added in fastly/go-fastly#764.All Submissions:
New Feature Submissions:
go.mod/go.sumupdated once there's ago-fastlyrelease that includes Supportmax_useandmax_lifetimebackend parameters go-fastly#764.Changes to Core Features:
go.mod/go.sumso that it builds.User Impact
This will allow users to further control how connection pooling works in both Delivery and Compute once the API is updated to account for these upcoming fields.
Are there any considerations that need to be addressed for release?
None that I'm aware of.