Visya

Running bash on a short-running stopped Docker container

If your Docker container is running a short command and you want to look inside it, sometimes it's really hard to do it, since docker exec doesn't run on stopped containers. What you can do is copy a container and run it with bash entrypoint.

docker ps -a -f "name=my-container"
docker commit my_container_id user/my-container
docker run -it --entrypoint bash user/my-container

Visya

Versioning in SNS messages

Message versioning can be required in SNS+SQS patternto allow setting up specific consumers that can process newer versions and make version transitions smooth and painless.

To achieve that you can use the native AWS SNS filtering mechanism. It allows to set version message attribute on a message sent to SNS and filter which queues receive which versions of messages.

Example of versioned message

Visya

Visya

async function getFilter(req) {
  const hasWildcardPermission = get(req, ['hasAccessTo', 'wildcard'], false);
  const networkIds = hasWildcardPermission ? null : get(req, ['hasAccessTo', 'networkId'], null);
  const { showIds: filterShowIds } = req.query;
  let showIds = null;

  if (hasWildcardPermission) {
    // if has access to everything, narrow networks to the shows from query
    if (filterShowIds.length) {
      const filteredNetworks = await getNetworksForShows(filterShowIds);

Visya

Retrieving permissions in client apps

Current model of permissions allows to grant a permission based on network id or show id, but some of the apps know how to work only with show ids. Also, we allow for wildcards, for example, this permission allows to view show in any app:

// *:read:show:showId
{
  app: '*',
  resource: 'show',
 action: 'read',

Visya

var name = 'Cat';

function Animal(name) {
  this.name = name;
  this.printName = function() {
    console.log(this.name);
  };
}

//const classFunctionCalled = Animal('Anything?');

Visya

// Permission
[
  {
    __t: 'Permission',
    id: 123,
    definition: 'manage:insights',
    params: ['showId']
  },
  {
    __t: 'Permission',

Visya

npm i -D -E husky@latest &&
npm i -D -E @commitlint/{cli,config-conventional} &&
npm i -D -E commitizen cz-conventional-changelog &&
npm i -D -E @semantic-release/{commit-analyzer,git,npm,release-notes-generator} semantic-release semantic-release-docker

package.json

  "private": true,

Visya

export MFA_ARN=YOUR_MFA_ARN
alias refreshtoken="AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY AWS_SESSION_TOKEN= ~/tools/aws-auth.sh"

source /tmp/aws-temp-creds.sh || echo "No AWS credentials found"

if ! aws iam get-user &> /dev/null; then
  refreshtoken
  source /tmp/aws-temp-creds.sh
fi

Visya

Useful Flutter resources

State management

Scoped models: https://proandroiddev.com/you-might-not-need-redux-the-flutter-edition-9c11eba006d7