open-index/open-npm huggingface dataset:
npm package: @ica-dev/brand
Description: ICA Brand
Author: Acando
Latest version: 0.0.3

# ica-brand

This is the global settings package for building JavaScript-based frontend projects on ICA.

The package contains:
- colors
- font sizes
- `font-face.css`: - import this into your project to gain access to the `@font-face` declarations, then serve the fonts from `/static/fonts/font.woff2`
- spacing: ICAs base 8 spacing list
- transitions: basic cubic-bezier functions
- breakpoints: a list of breakpoints ranging from mobile to tablet to desktop
- z-indexes: an ordered list with a 10 interval is generated from a `string[]`, followed by custom z-indexes

There are also a couple of utility functions related to creating components with Styletron
- media
- pseudo
npm package: @icalialabs/aws-configure-elb-rule
Description: Configures DNS records in a given AWS Route 53 domain
Author: Icalia Labs
Latest version: 0.0.1

# AWS Configure ELB Rule

Configures a given ELB Rule

## Usage

```yaml
      - name: Configure AWS ELB Rule
        uses: icalia-actions/aws-configure-elb-rule@v0.0.1
        with:
          listener: arn:YOUR_LISTENER_ARN
          
          # You can define the conditions, actions and tags using JSON or YAML:
          conditions: |  
            - Field: host-header
              HostHeaderConfig:
                Values:
                  - subdomain1.your-domain.tld
                  - subdomain2.your-domain.tld
          actions: |
            - Type: forward
              TargetGroupArn: arn:YOUR_TARGET_GROUP_ARN
          
          # You can optionally set a priority. By default, we'll get the lowest
          # priority and set a lower priority than that:
          priority: 15

          tags: |
            - Key: app
              Value: my-app
            - Key: environment
              Value: development
            - Key: pull-request-node-id
              Value: A_NODE_ID_FROM_GITHUB
```

### Using template files instead:

You can also use an optional json or yaml files for `conditions`, `actions` and
`tags` like this:

```yaml
# tmp/example-conditions.yml
- Field: host-header
  HostHeaderConfig:
    Values:
      - subdomain1.your-domain.tld
      - subdomain2.your-domain.tld
```

```yaml
# tmp/example-actions.yml
- Type: forward
  TargetGroupArn: arn:YOUR_TARGET_GROUP_ARN
```

```yaml
      - name: Configure AWS ELB Rule
        uses: icalia-actions/aws-configure-elb-rule@v0.0.1
        with:
          listener: arn:YOUR_LISTENER_ARN
          conditions: tmp/example.yml
          actions: tmp/example-actions.yml
```
npm package: @icalialabs/aws-configure-elb-target-group
Description: Finds or creates an AWS ELB Target Group
Author: Icalia Labs
Latest version: 0.0.3

# AWS ELB Configure Target Group

Finds or creates an AWS ELB Target Group

## Usage

```yaml
      - name: Configure AWS ELB Target Group
        uses: icalia-actions/aws-configure-elb-target-group@v0.0.2
        with:
          name: my-target-group
          port: "80"
          protocol: HTTP
          target-type: ip
          vpc-id: vpc-00000001
          health-check-path: /health
```
npm package: @icalialabs/aws-configure-route53-records
Description: Configures DNS records in a given AWS Route 53 domain
Author: Icalia Labs
Latest version: 0.0.1

# AWS Configure Route53 Records

Configures DNS records in a given AWS Route 53 domain

## Usage

```yaml
      - name: Configure AWS Route53 Records
        uses: icalia-actions/aws-configure-route53-records@v0.0.1
        with:
          hosted-zone-id: ROUTE53_HOSTED_ZONE_ID
          records: |
            [
              {
                "Name": "record-name.your-domain.tld.",
                "Type": "A",
                "AliasTarget": {
                  "HostedZoneId": "TARGET_HOSTED_ZONE_ID",
                  "DNSName": "dualstack.my-load-balancer.my-region.elb.amazonaws.com.",
                  "EvaluateTargetHealth": true
                }
              }
            ]
          comment: An optional comment that describes the purpose of these changes
```

### Using record template files:

You can also use an additional json or yaml file like this:

```yaml
# tmp/example.yml
- Name: subdomain1.my-domain.tld.
  Type: A
  AliasTarget: &target
    HostedZoneId: TARGET_HOSTED_ZONE_ID
    DNSName: dualstack.my-load-balancer.my-region.elb.amazonaws.com.
    EvaluateTargetHealth: true

- Name: subdomain2.my-domain.tld.
  Type: A
  AliasTarget:
    <<: *target
```

```yaml
      - name: Configure AWS Route53 Records
        uses: icalia-actions/aws-configure-route53-records@v0.0.1
        with:
          hosted-zone-id: ROUTE53_HOSTED_ZONE_ID
          records: tmp/example.yml
          comment: An optional comment that describes the purpose of these changes
```
npm package: @icalialabs/aws-delete-ecs-service
Description: Deletes a specified service within a cluster
Author: Icalia Labs
Latest version: 0.0.1

# AWS Delete ECS Service

Deletes a specified service within a cluster

## Usage

```yaml
      - name: Delete AWS ECS Service
        uses: icalia-actions/aws-delete-ecs-service@v0.0.1
        with:
          target-group: my-target-group
```
npm package: @icalialabs/aws-delete-elb-rule
Description: Deletes an AWS ELB using either a Rule ARN or the matching rules to remove
Author: Icalia Labs
Latest version: 0.0.1

# AWS Delete ELB Rule

Deletes an ELB Rule that matches a given parameter

## Usage

You can use `tags` (the best choice), `conditions` and/or `actions` for the
action to match the rule you want to delete:

```yaml
      - name: Delete AWS ELB Rule
        uses: icalia-actions/aws-delete-elb-rule@v0.0.1
        with:
          listener: arn:YOUR_LISTENER_ARN
          
          # You can define the tags using JSON or YAML:
          tags: |
            - Key: app
              Value: my-app
            - Key: environment
              Value: development
            - Key: pull-request-node-id
              Value: A_NODE_ID_FROM_GITHUB
```

### Using template files instead:

You can also use an optional json or yaml files for `conditions`, `actions` and
`tags` like this:

```yaml
# tmp/example-conditions.yml
- Field: host-header
  HostHeaderConfig:
    Values:
      - subdomain1.your-domain.tld
      - subdomain2.your-domain.tld
```

```yaml
# tmp/example-actions.yml
- Type: forward
  TargetGroupArn: arn:YOUR_TARGET_GROUP_ARN
```

```yaml
      - name: Delete AWS ELB Rule
        uses: icalia-actions/aws-delete-elb-rule@v0.0.1
        with:
          listener: arn:YOUR_LISTENER_ARN
          conditions: tmp/example.yml
          actions: tmp/example-actions.yml
```

See [icalia-actions/aws-configure-elb-rule](https://github.com/icalia-actions/aws-configure-elb-rule) to see how to create a rule
npm package: @icalialabs/aws-delete-elb-target-group
Description: Finds or creates an AWS ELB Target Group
Author: Icalia Labs
Latest version: 0.0.1

# AWS Delete ELB Target Group

Deletes an AWS ELB Target Group using either a Rule ARN or the matching rules to remove

## Usage

```yaml
      - name: Delete AWS ELB Target Group
        uses: icalia-actions/aws-delete-elb-target-group@v0.0.1
        with:
          target-group: my-target-group
```
npm package: @icalialabs/aws-delete-route53-records
Description: Deletes an AWS ELB using either a Rule ARN or the matching rules to remove.
Author: Icalia Labs
Latest version: 0.0.1

# AWS Delete Route53 Records

Deletes DNS records in a given AWS Route53 Hosted Zone

## Usage

```yaml
      - name: Delete AWS Route53 Records
        uses: icalia-actions/aws-delete-route53-records@v0.0.1
        with:
          hosted-zone-id: ROUTE53_HOSTED_ZONE_ID
          records: |
            [
              {
                "Name": "record-name.your-domain.tld.",
                "Type": "A",
                "AliasTarget": {
                  "HostedZoneId": "TARGET_HOSTED_ZONE_ID",
                  "DNSName": "dualstack.my-load-balancer.my-region.elb.amazonaws.com.",
                  "EvaluateTargetHealth": true
                }
              }
            ]
          comment: An optional comment that describes the purpose of the removal
```

### Using record template files:

You can also use an additional json or yaml file like this:

```yaml
# tmp/example.yml
- Name: subdomain1.my-domain.tld.
  Type: A
  AliasTarget: &target
    HostedZoneId: TARGET_HOSTED_ZONE_ID
    DNSName: dualstack.my-load-balancer.my-region.elb.amazonaws.com.
    EvaluateTargetHealth: true

- Name: subdomain2.my-domain.tld.
  Type: A
  AliasTarget:
    <<: *target
```

```yaml
      - name: Configure AWS Route53 Records
        uses: icalia-actions/aws-delete-route53-records@v0.0.1
        with:
          hosted-zone-id: ROUTE53_HOSTED_ZONE_ID
          records: tmp/example.yml
          comment: An optional comment that describes the purpose of the removal
```
npm package: @icalialabs/aws-deregister-ecs-task-definitions
Description: De-registers task definitions from AWS ECS
Author: Icalia Labs
Latest version: 0.0.1

# AWS Deregister ECS Task Definitions

De-registers task definitions from AWS ECS.

## Usage

```yaml
      - name: De-register AWS ECS Task Definitions
        uses: icalia-actions/aws-deregister-ecs-task-definitions@v0.0.1
        with:
          # You can use the family name, the definition (family name + version),
          # or the full task definition ARN:
          definition: my-task-definition
```
npm package: @icalialabs/cc-test-reporter-base
Description: Base commands to run the Code Climate Test Reporter on Github Actions
Author: Icalia Labs
Latest version: 0.0.2

# CodeClimate Test Reporter Base Github Action

Reports test coverage data to CodeClimate

## Usage

```yaml
      - name: Code Climate Test Reporter
        uses: icalia-actions/cc-test-reporter-base@v0.0.1
        with:
          command: before-build
```
npm package: @icalialabs/deploy-aws-ecs-service
Description: Deploys a Task Definition as a Service in AWS ECS
Author: Icalia Labs
Latest version: 0.0.7

# Deploy AWS ECS Service

Deploys a Task Definition as a Service in AWS ECS

## Usage

```yaml
      - name: Deploy AWS ECS Service
        uses: icalia-actions/deploy-aws-ecs-service@v0.0.1
        with:
          name: my-service
          cluster: my-cluster
          template: templates/ecs/my-service.json

          # You can optionally specify the desired task count:
          desired-count: 1

          # If you provide a task definition template, it will get registered:
          definition-template: templates/ecs/my-task-definition.json

          # You can override the image used on any container - the most common
          # use case is to deploy an image built & pushed on a previous step:
          container-images: '{"my-container":"my-built-image"}'

          # You can optionally override any environment variable in the task 
          # container definitions, given that the overriden environment variable
          # already exists in the container definition:
          environment-vars: '{"FOO":"BAR"}'

          # You can also override secrets already defined in the "secrets" key
          # inside the container definition by using a map consisting of the
          # "name" as key, and the "valueFrom" as the value - the secret name
          # *must* be present in the definition, otherwise it will be ignored.
          secrets: '{"MY_SECRET":"some-secret-name"}'

          # If your service must be associated with any number of load
          # balancers, you can specify those using a JSON array:
          load-balancers: |-
            [
              {
                "targetGroupArn":"my-target-group-arn",
                "containerName":"my-container-name",
                "containerPort":3000
              },
              {
                "loadBalancerName":"my-classic-load-balancer",
                "containerName":"my-container-name",
                "containerPort":3000
              }
            ]
```
npm package: @icalialabs/register-aws-ecs-task-definition
Description: Registers a Task Definition in AWS ECS
Author: Icalia Labs
Latest version: 0.0.14

# Register AWS ECS Task Definition

Registers a Task Definition in AWS ECS

## Github Action Usage

```yaml
      - name: Register AWS ECS Task Definition
        uses: icalia-actions/register-aws-ecs-task-definition@v0.0.1
        with:
          family: my-task-definition-family
          template: templates/ecs/my-task-definition.yml

          # You can override the image used on any container - the most common
          # use case is to deploy an image built & pushed on a previous step:
          container-images: '{"my-container":"my-built-image"}'

          # You can optionally override any environment variable in the task 
          # container definitions, given that the overridden environment variable
          # already exists in the container definition:
          environment-vars: '{"FOO":"BAR"}'

          # You can also override secrets already defined in the "secrets" key
          # inside the container definition by using a map consisting of the
          # "name" as key, and the "valueFrom" as the value - the secret name
          # *must* be present in the definition, otherwise it will be ignored.
          secrets: '{"MY_SECRET":"some-secret-name"}'
```

## Library Usage

```
yarn add --dev @icalialabs/register-aws-ecs-task-definition
```
npm package: @icalialabs/run-aws-ecs-task
Description: Runs a Task in AWS ECS
Author: Icalia Labs
Latest version: 0.0.5

# Run AWS ECS Task

Runs a Task in AWS ECS

## Github Action Usage

```yaml
      - name: Run AWS ECS Task
        uses: icalia-actions/run-aws-ecs-task@v0.0.2
        with:
          cluster: my-cluster
          
          # The name of the task to run - it will also be used as the name of
          # the task definition:
          name: my-cool-task

          # You may optionally wait until the task finishes (defaults to false)
          wait-to-completion: true
          
          # The template for the task - i.e. the json/yaml used when running
          # `aws ecs run-task --cli-input-yaml file://templates/ecs/my-task.yml`
          template: templates/ecs/my-task.yml

          # You can optionally set the task definition template:
          definition-template: templates/ecs/my-task-definition.yml

          # You can override the image used on any container - the most common
          # use case is to deploy an image built & pushed on a previous step:
          container-images: '{"my-container":"my-built-image"}'

          # You can optionally override any environment variable in the task 
          # container definitions, given that the overridden environment variable
          # already exists in the container definition:
          environment-vars: '{"FOO":"BAR"}'

          # You can also override secrets already defined in the "secrets" key
          # inside the container definition by using a map consisting of the
          # "name" as key, and the "valueFrom" as the value - the secret name
          # *must* be present in the definition, otherwise it will be ignored.
          secrets: '{"MY_SECRET":"some-secret-name"}'
```

## Library Usage

```
yarn add --dev @icalialabs/run-aws-ecs-task
```
npm package: @icalialabs/run-ci-compose
Description: Runs Docker Compose using an additional config file called 'ci-compose.yml'
Author: Icalia Labs
Latest version: 0.0.2

# Run ci-compose

Runs a Docker Compose service defined in a custom compose file called "ci-compose.yml"

## Usage

Given the following `docker-compose.yml` file - your case may vary:

```yaml
version: "3.7"

volumes:
  postgres_data:

services:
  postgres:
    image: postgres:13-alpine
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_PASSWORD: 3x4mpl3P455w0rd
```

And given the following `ci-compose.yml` file exists:

```yaml
version: "3.7"

services:
  tests:
    image: my-namespace/my-app:testing
    build:
      context: .
      target: testing
    depends_on:
      - postgres
    command: rspec
    volumes:
      - .:/demo
    environment:
      RAILS_ENV: test
      DATABASE_URL: postgres://postgres:3x4mpl3P455w0rd@postgres:5432/?encoding=unicode
```

### Github Action Usage

```yaml
      - name: Run Tests
        uses: icalia-actions/run-ci-compose@v0.0.1
        with:
          service-name: tests
```

### Library Usage

```
yarn add --dev @icalialabs/run-ci-compose
```