Support usage of IAM role in S3 and Kinesis logging endpoints #403
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
* Add the ability to specify an IAM role for the S3 and Kinesis logging endpoints * Bump go-fastly to v3.6.0
kellymclaughlin
force-pushed
the
aws-iam-role-support
branch
from
5b586b5 to
33e6fab
Compare
Integralist
requested changes
Apr 21, 2021
Integralist
approved these changes
Apr 23, 2021
|
@Integralist: Apologies for potentially misappropriating this PR's comments. Also, do y'all have any general timeline for when a release containing these additions will land (and/or any published documentation on this provider's release timeline / cadence)? |
|
Hi @jeffwecan 👋🏻
That's OK 🙂 Apologies for the slow reply, but I've been away on leave. I'll be cutting a new release this morning. |
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.
Follows from fastly/go-fastly#269.