BEARER=$(curl -u _token:$(gcloud auth print-access-token) https://gcr.io/v2/token?scope=repository:$NAME:pull | cut -d'"' -f 10) RESPONSE=`curl -H "Authorization: Bearer $BEARER" https://gcr.io/v2/$NAME/manifests/$TAG` DIGEST=`echo $RESPONSE | jq -r '.config.digest'` curl -L -H "Authorization: Bearer $BEARER" https://gcr.io/v2/$NAME/blobs/$DIGEST | jq
|replicas: 2 # tells deployment to run 2 pods matching the template|
|- uri: /service-A/v1|
|- uri: /service-A/v2|
GCP cached permissions issue
GCP has an issue which surfaces when service accounts are recreated with the same name but without the old policies being removed. It is confusing because the GUI and CLI will show that permissions are there and it will even let you re-add them BUT, anytime you try to do something that requires the permissions it won't work. For example, if you try to push an image it may say that you don't have
storage.buckets.get even thought everything shows that you are part of
Reproducing the issue
Set the values to match your environment
serverless-stack.com with SAM
...as an alternative to the Serverless Framework.
- SAM templates result in Cloudformation stacks. This has a benefit of ensuring all the resoures are defined together and allows the management from a GUI.
- SAM requires that IAM policies to be defined at the function level rather than globally as per the Serverless Framework. According to the SAM docs, this was a design decision to reduce the risk of functions being granted more permissions than they need.
- Enabling CORS in SAM requires the specific allowed methods and headers to be provided. This is as opposed to Serverless Framework where it is just an on/off flag.
- SAM supports parameters to be passed to the template at deploy/test-time. Serverless Framework achieves this with environment variables.
CouchDb from http://couchdb.apache.org
Inkdrop from https://my.inkdrop.app/download
Synchronisation steps at https://docs.inkdrop.app/manual/synchronizing-in-the-cloud
Access CouchDb from http://127.0.0.1:5984/_utils/
- API-lead connectivity: A methodical way to connect applications, data, and devices through reusable and purposeful APIs; the opposite of point-to-point integration.
- Application Network: A network of applications, data, and devices connected by reusable APIs, each built with the principles of API-led connectivity.
- Anypoint Platform: MuleSoft's platform that provides many tools to design, build, deploy, and operate the application network.
- System APIs: unlock data from systems
- Process APIs: compose data into processes
- Experience APIs: deliver an experience
How to fix breaking change in the AWS developer preview SDK for Go on the client side
A recent commit resulted in a change in naming convention for the client struct. The below is tested on Mac OS X, not sure if it needs adjustment for linux distros or not. This is not an exhaustive fix, it just fixes the APIs that I was using in my projects.
find . -type f -name "*.go" | xargs sed -i '' 's/s3\.S3/s3.Client/g' find . -type f -name "*.go" | xargs sed -i '' 's/cloudfront\.CloudFront/cloudfront.Client/g' find . -type f -name "*.go" | xargs sed -i '' 's/dynamodb\.DynamoDB/dynamodb.Client/g'