github cloudposse/geodesic 0.141.1
v0.141.1
on GitHub

latest releases: 3.4.0, 3.3.0, 3.2.0...
3 years ago

🚀 Enhancements

Fix Terraform plugin cache, bastion host login user @Nuru (#669)

what

  1. Change location of Terraform plugin cache from $HOME/.terraform.d/plugins to $HOME/.terraform.d/plugin-cache
  2. [kopsctl] Change bastion host login user from admin to ubuntu
  3. Restore KUBECONFIG environment variable
  4. Ensure $KUBCONFIG exists with no group or world read permissions
  5. Attempt to disable dependabot PRs

why

  1. $HOME/.terraform.d/plugins is an implied Terraform mirror directory and using it as a plugin cache breaks both the cache and the mirror
  2. kops switched default OS from Debian (with default user admin) to Ubuntu (with default user ubuntu)
  3. Kubernetes prompt from kube-ps1 is disabled if $KUBECONFIG is empty at startup, and kubectl complains if $KUBECONFIG does not exist
  4. kubectl complains if $KUBECONFIG is group or world readable
  5. Not sure exactly why or how dependabot PRs were enabled, but they duplicate the PRs created by Renovate, so they add unnecessary noise

notes

Officially, $KUBECONFIG is a list of possible files to use for configuration, but Geodesic assumes in many places that it points to only a single file. (Issue #457)

references

🧰 Included Tools

Update dependency ansible to v2.10.5 @renovate (#668)

This PR contains the following updates:

Package Update Change
ansible (source) patch ==2.10.4 -> ==2.10.5
Update AWS CLI packages @renovate (#665)

This PR contains the following updates:

Package Update Change
awscli patch ==1.18.199 -> ==1.18.216
boto3 patch ==1.16.39 -> ==1.16.56

Release Notes

boto/boto3

v1.16.56

Compare Source

=======

  • api-change:sns: [botocore] Update sns client to latest version

v1.16.55

Compare Source

=======

  • api-change:pinpoint: [botocore] Update pinpoint client to latest version
  • api-change:cognito-identity: [botocore] Update cognito-identity client to latest version
  • api-change:s3control: [botocore] Update s3control client to latest version
  • api-change:sagemaker: [botocore] Update sagemaker client to latest version

v1.16.54

Compare Source

=======

  • api-change:frauddetector: [botocore] Update frauddetector client to latest version
  • api-change:personalize: [botocore] Update personalize client to latest version

v1.16.53

Compare Source

=======

  • api-change:appstream: [botocore] Update appstream client to latest version
  • api-change:auditmanager: [botocore] Update auditmanager client to latest version
  • api-change:ssm: [botocore] Update ssm client to latest version
  • api-change:elasticache: [botocore] Update elasticache client to latest version
  • api-change:lightsail: [botocore] Update lightsail client to latest version

v1.16.52

Compare Source

=======

  • api-change:rds: [botocore] Update rds client to latest version
  • api-change:kms: [botocore] Update kms client to latest version

v1.16.51

Compare Source

=======

  • api-change:devops-guru: [botocore] Update devops-guru client to latest version
  • api-change:codepipeline: [botocore] Update codepipeline client to latest version
  • api-change:mediaconvert: [botocore] Update mediaconvert client to latest version

v1.16.50

Compare Source

=======

  • api-change:autoscaling: [botocore] Update autoscaling client to latest version
  • api-change:transfer: [botocore] Update transfer client to latest version
  • api-change:autoscaling-plans: [botocore] Update autoscaling-plans client to latest version

v1.16.49

Compare Source

=======

  • api-change:ce: [botocore] Update ce client to latest version
  • api-change:application-autoscaling: [botocore] Update application-autoscaling client to latest version

v1.16.48

Compare Source

=======

  • api-change:healthlake: [botocore] Update healthlake client to latest version
  • api-change:cloudsearch: [botocore] Update cloudsearch client to latest version

v1.16.47

Compare Source

=======

  • api-change:servicecatalog: [botocore] Update servicecatalog client to latest version

v1.16.46

Compare Source

=======

  • api-change:macie2: [botocore] Update macie2 client to latest version
  • api-change:elasticache: [botocore] Update elasticache client to latest version

v1.16.45

Compare Source

=======

  • api-change:acm-pca: [botocore] Update acm-pca client to latest version
  • api-change:apigatewayv2: [botocore] Update apigatewayv2 client to latest version

v1.16.44

Compare Source

=======

  • api-change:cloudfront: [botocore] Update cloudfront client to latest version

v1.16.43

Compare Source

=======

  • api-change:compute-optimizer: [botocore] Update compute-optimizer client to latest version
  • api-change:resource-groups: [botocore] Update resource-groups client to latest version
  • api-change:dms: [botocore] Update dms client to latest version

v1.16.42

Compare Source

=======

  • api-change:ssm: [botocore] Update ssm client to latest version
  • api-change:iotwireless: [botocore] Update iotwireless client to latest version
  • api-change:rds: [botocore] Update rds client to latest version
  • api-change:glue: [botocore] Update glue client to latest version
  • api-change:ce: [botocore] Update ce client to latest version
  • api-change:connect: [botocore] Update connect client to latest version
  • api-change:elasticache: [botocore] Update elasticache client to latest version

v1.16.41

Compare Source

=======

  • api-change:config: [botocore] Update config client to latest version
  • api-change:ec2: [botocore] Update ec2 client to latest version
  • api-change:glue: [botocore] Update glue client to latest version
  • api-change:batch: [botocore] Update batch client to latest version
  • api-change:managedblockchain: [botocore] Update managedblockchain client to latest version
  • api-change:service-quotas: [botocore] Update service-quotas client to latest version
  • api-change:s3: [botocore] Update s3 client to latest version
  • api-change:connectparticipant: [botocore] Update connectparticipant client to latest version
  • api-change:securityhub: [botocore] Update securityhub client to latest version
  • api-change:qldb-session: [botocore] Update qldb-session client to latest version
  • api-change:outposts: [botocore] Update outposts client to latest version
  • api-change:servicecatalog-appregistry: [botocore] Update servicecatalog-appregistry client to latest version
  • api-change:dms: [botocore] Update dms client to latest version
  • api-change:apigateway: [botocore] Update apigateway client to latest version

v1.16.40

Compare Source

=======

  • api-change:rds: [botocore] Update rds client to latest version
  • bugfix:SSO: [botocore] Fixed timestamp format for SSO credential expirations
  • api-change:personalize-runtime: [botocore] Update personalize-runtime client to latest version
  • api-change:ec2: [botocore] Update ec2 client to latest version

🏗️ Build/Release Maintenance

Fix Terraform plugin cache, bastion host login user @Nuru (#669)

what

  1. Change location of Terraform plugin cache from $HOME/.terraform.d/plugins to $HOME/.terraform.d/plugin-cache
  2. [kopsctl] Change bastion host login user from admin to ubuntu
  3. Restore KUBECONFIG environment variable
  4. Ensure $KUBCONFIG exists with no group or world read permissions
  5. Attempt to disable dependabot PRs

why

  1. $HOME/.terraform.d/plugins is an implied Terraform mirror directory and using it as a plugin cache breaks both the cache and the mirror
  2. kops switched default OS from Debian (with default user admin) to Ubuntu (with default user ubuntu)
  3. Kubernetes prompt from kube-ps1 is disabled if $KUBECONFIG is empty at startup, and kubectl complains if $KUBECONFIG does not exist
  4. kubectl complains if $KUBECONFIG is group or world readable
  5. Not sure exactly why or how dependabot PRs were enabled, but they duplicate the PRs created by Renovate, so they add unnecessary noise

notes

Officially, $KUBECONFIG is a list of possible files to use for configuration, but Geodesic assumes in many places that it points to only a single file. (Issue #457)

references

Limit AWS CLI updates to once a week @Nuru (#664)

what

  • Limit aws CLI and boto3 updates to once a week and group them together

why

  • Reduce the noise. In general these are updated several times a week but the updates are not urgent.
  • Group them because they are typically released together (since aws depends on boto3) and aws pins boto3 in such a way that the boto3 update would break aws if aws is not updated at the same time.
Check out latest releases or
releases around cloudposse/geodesic 0.141.1

Don't miss a new geodesic release

NewReleases is sending notifications on new releases.

Get notifications