Kyle Knapp

Software engineer. Python & AI. Microsoft. Opinions are my own.

[Marlene Mhangami @marlene_zw]

Our awesome storage team is also working to update the all our Azure related document loaders in @langchain too🦜❤️ I'll share a blog post about this work soon but we'd like feedback from the community are collecting it here🤗:

https://t.co/QqcnyS8lkY

[Kyle Knapp @thekyleknapp]

The AWS CLI team is updating the "configure sso" command to support configuring "sso-session" shared config sections (i.e. named, reusable SSO configuration groups). Feedback is encouraged on the proposed configuration flow! See PR to try it out: https://t.co/r193mpT6wY

[Kyle Knapp @thekyleknapp]

In the video, I'm manually updating to the latest AL2022 release to install v2 since I'm running on an older release of AL2022. But once the 2022-06-28 AL2022 release is built out into a public AMI, instances spun up from that AMI should have v2 already installed.

[Kyle Knapp @thekyleknapp]

The latest release of Amazon Linux 2022 now defaults to AWS CLI v2!

[Kyle Knapp @thekyleknapp]

@ben11kehoe @_msw_ @mattbonig Moving forward, the team will be putting much more effort into reviewing GitHub PRs. We plan to use this proposed process to help drive our effort and community contributions.

[Kyle Knapp @thekyleknapp]

@ben11kehoe @_msw_ @mattbonig Following up here... We just published a proposal defining a better process for managing AWS CLI community contributions. Feedback is encouraged! https://t.co/HUzoBLolUI

[none @sleight82]

👋🏻 #AWS users! We published a proposal to improve how we manage community contributions for the AWS CLI. Please check out this GitHub PR to learn more about what we’re thinking; feedback on your experience is appreciated! https://t.co/DtomKwH9sD

[Kyle Knapp @thekyleknapp]

3. Mechanism to make sure the team sees a PR through to completion if the PR has entered the full review stage and progress stalled in updating the PR based on review feedback.

[Kyle Knapp @thekyleknapp]

Check out this AWS CLI proposal defining a better process for managing community contributions/PRs. Moving forward, the team will be putting much more effort into reviewing GitHub PRs. We plan to use this proposed process to help drive our effort and community contributions.

[none @sleight82]

👋🏻 #AWS users! We published a proposal to improve how we manage community contributions for the AWS CLI. Please check out this GitHub PR to learn more about what we’re thinking; feedback on your experience is appreciated! https://t.co/DtomKwH9sD

[Kyle Knapp @thekyleknapp]

2. GitHub project board and public prioritization of our PR review queue to establish clearer communication where in the contribution lifecycle a PR stands and when to expect a PR to be reviewed relative to other community PRs.

[Kyle Knapp @thekyleknapp]

@esh We just released it as part of 2.5.1! https://t.co/SUjuAt0Xbr

[Kyle Knapp @thekyleknapp]

@mtdowling @rchrdbyd Yeah I'd definitely not recommend doing that in production. But it's neat to see a POC working with the CLI.

[Nate Prewitt @nateprewitt]

New blog post with updates around Python version support in the AWS CLI and Boto3. Deprecation timelines should now be more predictable, allowing easier planning.

https://t.co/BzEt7ghBDt

[Kyle Knapp @thekyleknapp]

@gccosgrove Fixed! Should be open now.

[Kyle Knapp @thekyleknapp]

The AWS CLI dev team is hiring! Posting is for NYC area but location is flexible. DM me if interested.
https://t.co/ELNwIZEwrm

[Kyle Knapp @thekyleknapp]

@rchrdbyd @ben11kehoe I'm all for it

[Kyle Knapp @thekyleknapp]

@ben11kehoe @_msw_ @mattbonig And in the end, help drive better communication/expectations and make sure we are at least reviewing/merging the smaller PRs. Thoughts?

[Kyle Knapp @thekyleknapp]

@ben11kehoe @_msw_ @mattbonig This hopefully would include SLAs for determining what we want to do with the PR (e.g., move forward with it, reject it, leave it up for community decision), what types of contributions we are willing to accept, and what to expect based on the type of contribution, etc.