Karan Kaw's Blog

Wednesday, July 7, 2021

The best strategy to avoid mixed content blocking is to serve all the content as HTTPS instead of HTTP.

AWS:CloudShell:CLI: aws ec2 describe-instances

https://thehftguy.com/2016/03/10/how-to-export-amazon-ec2-instances-to-a-csv-file/

https://gmusumeci.medium.com/how-to-export-aws-ec2-instances-in-multiple-aws-regions-and-multiple-aws-accounts-to-excel-csv-ce283af0ed90

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Filtering.html

https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html

https://docs.aws.amazon.com/cloudshell/latest/userguide/working-with-cloudshell.html

AWS Cloud Shell

aws ec2 describe-instances --filters "Name=tag:Environment,Values=QA" --output json

aws ec2 describe-instances --filters "Name=tag:Environment,Values=QA" --output table > QA_EC2_Instances.tsv

InstanceId

InstanceType

PrivateIpAddress

aws ec2 describe-instances \

--filters "Name=tag:Environment,Values=QA" \

--query 'Reservations[*].Instances[*].{InstanceId:InstanceId,InstanceType:InstanceType,PrivateIpAddress:PrivateIpAddress}' \

--output json \

> QA_EC2_Instances.json

aws ec2 describe-instances --filters Name=instance-state-name,Values=running --query "Reservations[*].Instances[*].InstanceId" --output text

aws iam list-access-keys --user-name john_doe

AWS : Exam:Practice Exam:Mock Exam: Cloud Practioner

https://geekflare.com/aws-practice-test/

https://digitalcloud.training/certification-training/

https://digitalcloud.training/certification-training/aws-certified-cloud-practitioner/

https://digitalcloud.training/courses/free-aws-certified-cloud-practitioner-practice-exam/

https://www.testpreptraining.com/

https://www.whizlabs.com/cart/

WELCOME

https://karanawsbucket.s3.us-east-1.amazonaws.com/Blogger_Images/products_whizcard-clf-c01-01-06.pdf

https://karanawsbucket.s3.us-east-1.amazonaws.com/Blogger_Images/products_csaa-whizcard-_-revised_14_06_2021.pdf

Azure : Devops : Pipeline :YAML

You can organize pipeline jobs into stages. Stages are the major divisions in a pipeline: "build this app", "run these tests", and "deploy to pre-production" are good examples of stages. They are logical boundaries in your pipeline where you can pause the pipeline and perform various checks.

Pipeline > Stages >Stage>Steps>Step

jobs:

- job: A

steps:

- bash: echo "A"

- job: B

steps:

- bash: echo "B"

If you organize your pipeline into multiple stages, you use the stages keyword.

If you choose to specify a pool at the stage level, then all jobs defined in that stage will use that pool unless otherwise specified at the job-level

stages:

- stage: A

jobs:

- job: A1

- job: A2

- stage: B

jobs:

- job: B1

- job: B2

When you define multiple stages in a pipeline, by default, they run sequentially in the order in which you define them in the YAML file. The exception to this is when you add dependencies. With dependencies, stages run in the order of the dependsOn requirements

stages:

- stage: string

dependsOn: string

condition: string

-----------------------------------------------------------

You can organize your pipeline into jobs. Every pipeline has at least one job. A job is a series of steps that run sequentially as a unit. In other words, a job is the smallest unit of work that can be scheduled to run.

In the simplest case, a pipeline has a single job. In that case, you do not have to explicitly use the job keyword

jobs:

- job: myJob

timeoutInMinutes: 10

pool:

vmImage: 'ubuntu-16.04'

steps:

- bash: echo "Hello world"

/usr/lib/jvm/adoptopenjdk-11-hotspot-amd64

# update-alternatives --config java

update-alternatives --list java

echo ls /etc/alternatives

ls /etc/alternatives

https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops

https://faun.pub/reduce-your-build-time-using-caching-in-azure-pipelines-7a7bd0201cee

MAVEN_CACHE_FOLDER: $(HOME)/.m2/repository"

variables:

MAVEN_CACHE_FOLDER: $(HOME)/.m2/repository

MAVEN_OPTS: '-Dmaven.repo.local=$(MAVEN_CACHE_FOLDER)'

- task: Cache@2

inputs:

key: '"funcs" | maven |"$(Agent.OS)" | **/pom.xml'

restoreKeys: |

path: $(MAVEN_CACHE_FOLDER)

displayName: Cache Maven local repo

https://stackoverflow.com/questions/66161852/is-there-a-predefined-variable-for-home-vsts-in-azure-pipelines/66161853#66161853

Pool: Hosted Ubuntu 1604

Agent: Hosted Agent

Pool: Azure Pipelines

Image: ubuntu-16.04

Agent: Hosted Agent

Azure : Devops : Pipelines: Task ::: Cache Task

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops

https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops#maven

Maven

Maven has a local repository where it stores downloads and built artifacts. To enable, set the maven.repo.local option to a path under $(Pipeline.Workspace) and cache this folder.

Example:

YAML

variables:
  MAVEN_CACHE_FOLDER: $(Pipeline.Workspace)/.m2/repository
  MAVEN_OPTS: '-Dmaven.repo.local=$(MAVEN_CACHE_FOLDER)'

steps:
- task: Cache@2
  inputs:
    key: 'maven | "$(Agent.OS)" | **/pom.xml'
    restoreKeys: |
      maven | "$(Agent.OS)"
      maven
    path: $(MAVEN_CACHE_FOLDER)
  displayName: Cache Maven local repo

- script: mvn install -B -e