| - name: Configure AWS Credentials | |
| uses: aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502 # v4.0.2 | |
| with: | |
| role-to-assume: ${{ env.AWS_WORKFLOW_ROLE }} | |
| role-session-name: ${{env.AWS_ROLE_SESSION_NAME}} | |
| aws-region: ${{env.AWS_REGION }} | |
| - name: Login to Amazon ECR | |
| id: login-ecr | |
| uses: aws-actions/amazon-ecr-login@062b18b96a7aff071d4dc91bc00c4c1a7945b076 #v2.01 | |
| - name: get ECR registry name |
Jako zaawansowany analityk biznesowy, posiadasz unikalne połączenie umiejętności analitycznych, strategicznego myślenia i głębokiego zrozumienia dynamiki biznesowej. Twoje zadania obejmują:
| #!/usr/bin/env zsh | |
| # Script Name: cancel_github_workflows.zsh | |
| # Description: This script cancels GitHub Actions workflows for a specific branch | |
| # that are either queued or in progress. | |
| # | |
| # Usage: ./cancel_github_workflows.zsh <branch_name> | |
| # | |
| # Arguments: | |
| # <branch_name>: The name of the branch for which to cancel workflows |
| org=<your org> | |
| repo=<your repo> | |
| # Get workflow IDs with status "disabled_manually" | |
| workflow_ids=($(gh api repos/$org/$repo/actions/workflows --paginate | jq '.workflows[] | select(.["state"] | contains("disabled_manually")) | .id')) | |
| for workflow_id in "${workflow_ids[@]}" | |
| do | |
| echo "Listing runs for the workflow ID $workflow_id" | |
| run_ids=( $(gh api repos/$org/$repo/actions/workflows/$workflow_id/runs --paginate | jq '.workflow_runs[].id') ) |
FWIW: I (@Rondy) am not the author of the content presented here, which is an outline from Edmond Lau's book. I've just copy-pasted it from somewhere and saved as a personal gist, before it got popular on newsnews.ycombinator.com. I don't remember where exactly the original source is from and neither could find the author's name, so I cannot give him/her the proper credits.
FWIW: I (@Rondy) am not the author of the content presented here, which is an outline from Edmond Lau's book. I've just copy-pasted it from somewhere and saved as a personal gist, before it got popular on newsnews.ycombinator.com. I don't remember where exactly the original source is from and neither could find the author's name, so I cannot give him/her the proper credits.
| Chai BDD assertions provide a more expressive and readable syntax compared to the assert library in Node.js. | |
| The BDD-style syntax resembles natural language, making the tests easier to understand and maintain. | |
| // Using Chai BDD assertions | |
| expect(foo).to.be.a('string'); | |
| expect(foo).to.have.lengthOf(3); | |
| expect(foo).to.equal('bar'); | |
| // Using Node.js assert library | |
| assert.strictEqual(typeof foo, 'string'); |
| const chai = require('chai'); | |
| const chaiHttp = require('chai-http'); | |
| const { afterEach, describe, it } = require('mocha'); | |
| chai.use(chaiHttp); | |
| const expect = chai.expect; | |
| // Server URL | |
| const serverUrl = 'http://localhost:3000'; |
| Scenario Outline: Convert IP address range to CIDR notation | |
| Given a range of IP addresses "<start_ip>" to "<end_ip>" | |
| When I convert the IP address range to CIDR notation | |
| Then the CIDR notation should be "<cidr_notation>" | |
| Examples: | |
| | start_ip | end_ip | cidr_notation | | |
| | 192.168.0.1 | 192.168.0.5 | 192.168.0.1/31 | | |
| | 10.0.0.0 | 10.0.0.255 | 10.0.0.0/24 | | |
| | 172.16.0.0 | 172.31.255.255 | 172.16.0.0/12 | |