Function to perform a deep copy of an object - rudimentary in that it will only handle the following types:
- Primitives
- Array
- Object
Basically can perform the following, but also copy undefined:
A pattern for using concurrent.futures.ThreadPoolExecutor() to execute a series of "worker" functions in parallel, processing a queue of assigned "work".
How it works:
worker_init() creates:
threading.Event() to denote "no more work in queue".futures.ThreadPoolExecutor().Python utility to bulk delete GitHub Actions runs for a given workflow, either current or legacy/since removed. The GitHub web UI currently allows removal of individual workflow runs - but this becomes tedious quickly when performed in bulk.
Create a Personal access token allowing the workflow scope:
Create a new Personal access token with the following permissions:
delete:packages
read:packages
write:packages
Minimal YAML configuration for enabling Dependabot within a Golang based repository.
Place dependabot.yaml at .github/dependabot.yaml within a target repository and you should be good to go.
Configuration dependabot-grouped.yaml implements package grouping, in this example all packages related to AWS Golang SDK with updates will be rolled up into a single Dependabot pull request.
| name: Workflow | |
| on: | |
| push: | |
| branches: | |
| - main | |
| jobs: | |
| first: | |
| runs-on: ubuntu-latest |
A guide for removing an existing CloudFormation stack - but retaining all managed resources.
First step - we need to get the CloudFormation stack into a state of DELETE_FAILED. This can be achieved by attempting stack delete with an IAM role that only has IAM action rights to cloudformation:DeleteStack and cloudformation:DescribeStackResources.
Create a new temporary IAM role with only the following allowed policy actions - for the rest of this guide that will be IAM role TEMP_CLOUDFORMATION_ROLE:
{Script has been handy to clean up security groups which have been used with VPC honed AWS Lambda functions and maintain an ENI association.
Why this is a problem:
AWS Lambda@Edge functions, which run under CloudFront at multiple edge locations require associated Lambda functions to exist within each AWS region.
By design, this means CloudWatch Log groups produced by Lambda@Edge functions will exist across these regions.
This Bash script will query for all log groups associated to Lambda@Edge functions for each enabled region of the current AWS account to hopefully help determine where logs are going to and/or exist.
Quick and dirty Bash script to iterate an S3 bucket and remove all object versions and delete markers.
Probably only usable on buckets with a few hundred version objects maximum, otherwise it might be more efficient and time effective to use a lifecycle rule to age out and remove objects in bulk.