foundweekends/giter8 1578
a command line tool to apply templates defined on GitHub
Scala at your command
softprops/action-gh-release 351
📦 :octocat: GitHub Action for creating GitHub Releases
send electronic mail with scala
sbt/sbt-bintray 180
fresh packages delivered from your sbt console
a publishing application for short texts
sbt/bintry 10
your packages, delivered fresh
Almost-realtime streaming APIs for train departure statuses
njtransit
Unfiltered template to use with servlet containers
pull request commentsoftprops/hubcaps
Looks good. Thanks @dt665m
comment created time in a day
push eventsoftprops/hubcaps
commit sha d11001bb6d80fc6a61dd8010b3d87752f4774184
add user emails struct and api to fetch them
commit sha 79d9f61375e95317df1e6f31d3c53996b9d54c97
added visibility to the UserEmail struct
commit sha b216117da1c7a61a9cbcb9b94ed3d0c53105d964
Merge pull request #278 from dt665m/auth-user-emails Auth user emails
push time in a day
PR merged softprops/hubcaps
<!--
- If there is a breaking or notable change please call that out as these will need to be added to the CHANGELOG.md file in this repository.
- This repository tries to stick with the community style conventions using rustfmt with the default settings. If you have custom settings you may find that rustfmt
clutter the diff of your change with unrelated changes. Please apply formatting with
cargo +nightly fmtbefore submitting a pr. -->
What did you implement:
- Added "fn authenticated_emails" and "UserEmail" struct in "src/users.rs", which fetches from github's "/user/emails"
- Added a usage example of the new function in "examples/users.rs" <!-- If this closes an open issue please replace xxx below with the issue number -->
Closes: #277
How did you verify your change:
- Since there isn't a generic test suite for api calls, I added it to "examples/users.rs" and eyeballed it.
What (if anything) would need to be called out in the CHANGELOG for the next release:
- A new users feature that allows getting "/user/emails"
pr closed time in a day
issue closedsoftprops/hubcaps
List authenticated user's emails
<!-- Please search existing issues to avoid creating duplicates. -->
💡 Feature description
By default, the authenticated user model will only grab the "publicly available email" of a specific user. Github also allows a user to have multiple linked emails with the "user:email" scope. It would be nice to have a method to grab the list of linked emails associated with the authenticated user's github account. since "github.get(...)" is private and there isn't a deserializable struct for the email model, this needs to be implemented. The specified github api is documented here: https://developer.github.com/v3/users/emails/ <!-- Describe the feature you'd like. -->
💻 Basic example
<!-- Include a basic code example if possible. Omit this section if not applicable. -->
for email in github.users().authenticated_emails().await? {
println!("verified: {:?}", email.verified);
println!("email: {:?}", email.email);
println!("primary: {:?}", email.primary)
println!("visibility: {:?}", email.visibility)
}
closed time in a day
dt665m
pull request commentsoftprops/dynomite
Add initial support for fat enums (internally-tagged representation)
Sorry about the delay. I've been caught up with a team transition at work. I just merged the last clean up pull and it seems there are now conflicts with these changes
comment created time in 3 days
push eventsoftprops/dynomite
commit sha 86b63e3506390a508f2933436f72a70a7d905473
Add support for internally-tagged fat enums
commit sha 40b9d87f1a70de3dd5ca49d717e50266cd8633ad
Cleanup From/IntoAttributes traits: Renamed `fn from_mut_attrs` to `fn from_attrs` and removed the previous impl. Now in order to convert items to/from attrs by consuming them users should use generated `TryFrom<Attributes>/Into<Attributes>` impls.
commit sha fbc946c0af6fe03e2b31e54ca4e6b0f54cc8c36c
Merge pull request #137 from Veetaha/feat/cleanup-from-into-attrs-traits Cleanup From/IntoAttributes traits
push time in 3 days
PR merged softprops/dynomite
Blocked by:
- #134
- #136
What did you implement:
Renamed fn from_mut_attrs to fn from_attrs and removed the previous impl.
Now in order to convert items to/from attrs by consuming them users should use
generated TryFrom<Attributes>/Into<Attributes> impls.
How did you verify your change:
Ran existing tests
What (if anything) would need to be called out in the CHANGELOG for the next release:
from_attrsnow takesAttributesby a&mutreference, usetry_from()for convenient consuming of the attr map
pr closed time in 3 days
starteddandavison/delta
started time in 3 days
issue openedScottBrenner/cfn-lint-action
Reconsider publishing a prebuild images
Please reconsider publishing a prebuilt image to a public docker registry. In one of my projects that use this action all other linting happens in seconds for a large repository. Since we're no longer able to use a pre-built docker image for this action, we have to wait at least a minute before the action can start doing any work. This build time was previous amortized with a prebuilt image which greatly reduced the feedback cycle time.
created time in 6 days
startedcharmbracelet/charm
started time in 8 days
startedcharmbracelet/glow
started time in 8 days
startedchriswalz/bit
started time in 13 days
issue commentsoftprops/turnstyle
That sounds reasonable. Just to confirm the difference would be failing the job rather than pressing on? That makes sense to me.
comment created time in 17 days
push eventsoftprops/turnstyle
commit sha 064db97f447a6010c20e1566830e47eb58548b7f
Update wait.ts Added a space between the <runid> and '...' in the 'Awaiting run https://github.com/<repo>/actions/runs/<runid>...' message so the link can be click (previously, the '...' were part of the url an hence the page would not load until you remove the '...' manually.
commit sha 5dc50da08603526a8ba00c9c8a18d4afa3f69e7d
Update wait.test.ts Adapted wait.tests.ts to cover the newly added ' ' in the awaiting message.
commit sha fd5272f237a99bc43814b2096721192846d95c3d
Merge pull request #17 from jensrieskamp-leanix/patch-1 Update wait.ts
push time in 17 days
PR merged softprops/turnstyle
Added a space between the <runid> and '...' in the 'Awaiting run https://github.com/<repo>/actions/runs/<runid>...' message so the link can be click (previously, the '...' were part of the url an hence the page would not load until you remove the '...' manually.
pr closed time in 17 days
pull request commentsoftprops/turnstyle
Sounds good
comment created time in 17 days
startedwatchexec/watchexec
started time in 21 days
push eventsoftprops/homebrew-tools
commit sha f5836e142d5cfbca5d89d3efb5b35909c5fa16a5
update sha
push time in 22 days
push eventsoftprops/homebrew-tools
commit sha 1337d0b7f8147f097c10b8b0132ff3aeb1fc2131
version bump
push time in 22 days
created tagsoftprops/aws-crossing
🚸 Do cross AWS account work more efficiently
created time in 22 days
push eventsoftprops/aws-crossing
commit sha dd90499cedb8dd32d16cdfb1a7bb98526efd99d0
version bump
push time in 22 days
issue closedsoftprops/aws-crossing
capture both stdout as well as stderr when a command exec fails
The aws cli namely logs output to stdout even when it errors. since we only print stderr when a run fails some useful details are not captured. Let's capture both streams for completeness
closed time in 22 days
softprops
push eventsoftprops/aws-crossing
commit sha 8876fdb4335c73e39f188ef25bc9cc02b2ddb010
combine stderr with stdout on err
commit sha 5e6a56ca09fe8aea39674d8ea2faea0a369ff6db
Merge pull request #6 from softprops/stdout-w-err combine stderr with stdout on err
push time in 22 days
push eventsoftprops/aws-crossing
commit sha 3404d5f86772f94fcbddf9478d525288798302cf
Revert "leverage tokio::spawn to do work on separate threads"
commit sha 467073930b6f2747f374541f885ad25a502afda9
Merge pull request #5 from softprops/revert-2-threaded Revert "leverage tokio::spawn to do work on separate threads"
push time in 22 days
PR merged softprops/aws-crossing
Reverts softprops/aws-crossing#2
pr closed time in 22 days
PR opened softprops/aws-crossing
Reverts softprops/aws-crossing#2
pr created time in 22 days
push eventsoftprops/aws-crossing
commit sha 10f70005976a6ac61bf7dc814bbe63a6befe667b
leverage tokio::spawn to do work on separate threads
commit sha d29bd2d4605a81e31749ef3db1321f492dc9f0f5
fix updated type
commit sha 20090fd311961335d947945ea9b7ee4c42815d6a
Merge pull request #2 from softprops/threaded leverage tokio::spawn to do work on separate threads
push time in 22 days
issue openedsoftprops/aws-crossing
some aws tools write to stdout when erroring
The aws cli namely logs output to stdout even when it errors. since we only print stderr when a run fails some useful details are not captured. Let's capture both streams for completeness
created time in 23 days
startedmeetup/BrazeTransifexServerless
started time in 23 days
push eventsoftprops/aws-crossing
commit sha d29bd2d4605a81e31749ef3db1321f492dc9f0f5
fix updated type
push time in a month
issue commentsoftprops/aws-crossing
Log AWS account id in which a command is run
👋 the capability is baked in if you need it. The account id is included as an environment variable named AWS_ACCOUNT_ID so in theory you could do something like
AWS_PROFILE=root aws-crossing \
--role AdminRole \
--command 'sh -c "echo $AWS_ACCOUNT_ID && aws cloudformation describe-stacks --stack-name example-stack --query 'Stacks[].StackStatus' --output text"'
if stringing commands becomes awkward you can always reference a script
AWS_PROFILE=root aws-crossing \
--role AdminRole \
--command 'test.sh'
cat test.sh
#!/bin/bash
echo Account $AWS_ACCOUNT_ID
aws cloudformation describe-stacks --stack-name example-stack --query 'Stacks[].StackStatus' --output text
comment created time in a month
push eventsoftprops/aws-crossing
commit sha f9c1fb68127d9857e5d913728638414fde7e830d
Update README.md
push time in a month
startedmuesli/duf
started time in a month
startedbenkonz/gameboy_emulator
started time in a month
push eventsoftprops/aws-crossing
commit sha 2fd64392ac971a6e89afd25cf7083e20ecf57fe1
update readme
push time in a month
created tagsoftprops/aws-crossing
🚸 Do cross AWS account work more efficiently
created time in a month
push eventsoftprops/aws-crossing
commit sha 4370f9ad1a09d01d10bab7a40c0470ccdde8b912
update changelog
commit sha a10359a42638a8853480a1b35f86181027c02256
update deps
commit sha fdef1ebfd12df4a805d422bb3b5c1c91fdaf2a19
simplify
push time in a month
push eventsoftprops/aws-crossing
commit sha 5a43d46471b0388298485915457b9aa50ba1b62a
Update README.md
push time in a month
push eventsoftprops/aws-crossing
commit sha 5b89c466279ab2420f3d185173b800e30ef2568b
Update README.md
push time in a month
push eventsoftprops/aws-crossing
commit sha 413e16ff7234834ae2a1e6ea96b981315640f236
More test updates
push time in a month
push eventsoftprops/aws-crossing
commit sha b8f77336db53e39f0a17ad9921f348c4a42095bd
Update tests
push time in a month
push eventsoftprops/aws-crossing
commit sha aa7966a46b323dac71fd62432db546808aec952b
Update tests
push time in a month
push eventsoftprops/aws-crossing
commit sha 4496467cfb8158d203add2ccc3eecce5e33389f7
use tokio::main defaults
push time in a month
push eventsoftprops/aws-crossing
commit sha d53661773d3ee5ef0dd79c7f3fc7a816dc99a82a
introduce logging and threaded tokio runtime
commit sha b5e5f1119766e5fab01a0b0b4dbc886eeae5851e
improve test coverage
push time in a month
starteddarklang/sync-async-benchmarks
started time in a month
pull request commentsoftprops/dynomite
Add initial support for fat enums (internally-tagged representation)
@Veetaha I'll try to follow up within the next week. I'm getting caught up with some things at work but I'll try to chew through this iteratively
comment created time in a month
push eventsoftprops/aws-crossing
commit sha a54707a23caf102d64b6cfc869ce5f9551276315
add notes for installing via homebrew
push time in a month
push eventsoftprops/homebrew-tools
commit sha 410b842d5bd50195218841e002594af706190c94
update aws-crossing sha
push time in a month
push eventsoftprops/homebrew-tools
commit sha 6d6e5c3bcde91f12832e5d9d516d7005c01544ea
add aws crossing
push time in a month
issue commentawslabs/aws-lambda-rust-runtime
unresolved import `lambda_attributes` when compiling with default-features = false
Should I use main or macro? What are the pro's and con's?
See the docs linked above it specifically calls out when not to use it and the tradeoff of when you are using it
comment created time in a month
push eventsoftprops/aws-crossing
commit sha 713e83f41fdf1d4d8b551e591a16e2e240a71a78
update readme example
push time in a month
created tagsoftprops/aws-crossing
🚸 Do cross AWS account work more efficiently
created time in a month
push eventsoftprops/aws-crossing
commit sha 5c31d485297406fb3932f3a8f4f238a6c8aea2de
move types to top
commit sha bc6cf563ba23a95edf74beaa723a6ec4052024fb
bump version
push time in a month
push eventsoftprops/aws-crossing
commit sha be927975d9745d9146cb3e8dabdd8acda13dd499
limit testing to stable rust. this is not a lib
push time in a month
push eventsoftprops/aws-crossing
commit sha 0b4f3702185f7350b738cf83a73b64c94f270b20
update name
push time in a month
push eventsoftprops/aws-crossing
commit sha 1dec297aad6aab0df89588fd8423c0c208ca03f8
readme formatting
push time in a month
push eventsoftprops/aws-crossing
commit sha 96a5025a02aa51a919545568aa16089296d3676c
update changelog
commit sha b357f44d815b7f4f2100554b7a17f36eca574242
dont do any release work unless its a tag
push time in a month
push eventsoftprops/aws-crossing
commit sha 81873caf5f491b7c6f03f35efd3b3cb495019042
update readme and fix clippy warning
push time in a month
push eventsoftprops/for-each-account
commit sha d660bcf07941fe3bda597c9de8ef6aebc3e76e89
rename
push time in a month
push eventsoftprops/for-each-account
commit sha 668923292fbc172caf9305777775ac72eb3ab306
update readme
push time in a month
push eventsoftprops/for-each-account
commit sha b4fbff7b8c4b3b7649392b2a413c8c216e782e8c
avoid nonempty command inputs
push time in a month
issue commentawslabs/aws-lambda-rust-runtime
unresolved import `lambda_attributes` when compiling with default-features = false
I feel like it's still useful. It's just a matter of documentation https://awslabs.github.io/aws-lambda-rust-runtime/lambda_http/#hello-world-without-macros
comment created time in a month
PR closed rusoto/rusoto
Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
experiment with #1553
pr closed time in a month
pull request commentrusoto/rusoto
kick the tires on GitHub actions
Closing I favor of https://github.com/rusoto/rusoto/pull/1821
comment created time in a month
issue openedsoftprops/for-each-account
remove aws cli dependency in favor of rusoto
the blocker for this is that rusoto doesn't natively support a useful feature profiles which assume roles.
[profile name-of-profile]
region = us-east-1
role_arn = arn:aws:iam::123456789:role/RoleToAssume
source_profile = default
created time in a month
push eventsoftprops/for-each-account
commit sha 04c4c9ad55eecb1ee1d9826da5eeed4e8ead2b3f
keep a changelog
commit sha 86fe95feea14ea832995433a79ef3695b9a6582e
update lock
push time in a month
push eventsoftprops/for-each-account
commit sha 9fcb881edc865bb7a24fa70be2b4661b8f608703
fmt
push time in a month
push eventsoftprops/for-each-account
commit sha df7d7b09a036e44c83bb12e8911529e04fe230bf
appease clippy
push time in a month
push eventsoftprops/for-each-account
commit sha 3b3638c37a9aa7d3a325545fbd4701067844bad2
cache cargo
push time in a month
push eventsoftprops/for-each-account
commit sha 7b1de17a043ac2246342a4f95441baf5cb68b4b2
fix workflow syntax err
push time in a month
push eventsoftprops/for-each-account
commit sha 24d506088c113c4397b4e5ac725afc2f5113917a
trigger build
push time in a month
push eventsoftprops/for-each-account
commit sha 13d4a27dc12232f797268f4d25011eb3591feed1
add workflow
push time in a month
pull request commentrusoto/rusoto
Wow it works! So exciting
comment created time in a month
issue openedaws/containers-roadmap
[Ecr] [request]: make image lifecycle policies ecs task aware
<!-- Please keep this note for the community -->
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!-- Thank you for keeping this note for the community -->
<!--
Security disclosures
If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.
-->
Tell us about your request
What do you want us to build?
Ecr image lifecycle policies are a great way cap cost associates with storing tagged docker images
However, lifecycle policies do not take into account active ecs task definitions which may refer to tags.
A lifecycle policy today can delete tags which a production ecs services uses which can case production outage when the service is unable to start tasks due to image pull backoff errors.
It should be possible to retain the value of using lifecycle policies and do less harm by excluding tags used by active ecs task definitions.
Which service(s) is this request for? ECS, ECR
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
We've ran into production stability issues with ecs services with task definitions which refer to ecr hosted docker images with lifecycle policies which get deleted. If the service kills of unhealthy tasks new tasks are not able go start due to the deletion of the docker image tag deleted.
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.
The outcome is retaining production stability while leveraging built in cost saving functionality at the same time.
This could potentially be worked around with a custom lambda which replaces the lifecycle policy feature of ecr. As a customer, I use the service so I don't have to manage and operate an additional service myself. Doing so decreases value I get out of the platform I pay for.
Are you currently working around this issue? How are you currently solving this problem?
Monitoring for ecs service instability caused by missing ecr hosted docker images and dealing with it manually.
Additional context
Anything else we should know?
Nopd
Attachments
N/A
created time in a month
push eventsoftprops/cred-lock
commit sha 2750f04dbe066dedc1a9ff1155b750fac41e8a81
const name for keychain
push time in a month
push eventsoftprops/dynomite
commit sha 3c998ac469fc83313588e8fa5488b1acee06bcf4
Impl attribute for FromAttributes + IntoAttributes
commit sha 9ba849c633d3d23fb31b52c0222905f508835902
Merge pull request #134 from Veetaha/feat/impl-attr-for-into-from-attrs Implement Attribute for FromAttributes + IntoAttributes
push time in a month
PR merged softprops/dynomite
Blocked by #132, merge that before reviewing and merging this
What did you implement:
Current constraint T: Item on the blanket impl is too restrictive, this PR relaxes that
How did you verify your change:
via CI
What (if anything) would need to be called out in the CHANGELOG for the next release:
Attributeis now implemented for any type that implementsFromAttributes + IntoAttributesinstead ofItem
pr closed time in a month
issue openedsoftprops/aws-credential-rotary
Add example using aws-actions/configure-aws-credentials
https://github.com/aws-actions/configure-aws-credentials is an action aws provides that exports a static or stay assumed set of credentials as workflow job env vars
For users of that action provides an example provide notes and example of how to pair with this action.
Notably if you use the configure action and then rotary the job scoped env credentials will have been invalidated via rotation. Let's make that clear in an experimental example
created time in a month
push eventsoftprops/aws-credential-rotary
commit sha 3f1ef697a7e6394b570877c6a02a2105c576bca9
refer to v1
commit sha 1bd5dbc4c6a19a36ba728fee49929c2bc44d61c2
a note about workflow serialization
push time in a month
push eventsoftprops/aws-credential-rotary
commit sha 0813ad4fd08f08497e814f96ac8638309b071996
how to rotate multiple credentials
push time in a month
push eventsoftprops/aws-credential-rotary
commit sha 1904eabd30c03ca458bd440b155e0274de45b425
we use the main branch, not master
commit sha 8cda4194f81bab61f2bbe127509b60a245b723d9
update docs
push time in a month