In the most basic scenario, you can use the[post operations]({{site.baseurl}}/docs/pipelines/post-step-operations/) of any Codefresh[step]({{site.baseurl}}/docs/pipelines/steps/) to add annotations:

In the most basic scenario, you can use the[post-step operations]({{site.baseurl}}/docs/pipelines/post-step-operations/) of any Codefresh[step]({{site.baseurl}}/docs/pipelines/steps/) to add annotations:

{% highlight yaml %}

{% include

image.html

lightbox="true"

file="/images/a0c4aed-codefresh_badges_2.png"

url="/images/a0c4aed-codefresh_badges_2.png"

file="/images/pipeline/badges/codefresh_badges.png"

url="/images/pipeline/badges/codefresh_badges.png"

alt="Codefresh badges syntax"

caption="Codefresh badges syntax"

max-width="70%"

toc:true

To access your global pipeline settings navigate to[https://g.codefresh.io/account-admin/account-conf/pipeline-settings](https://g.codefresh.io/account-admin/account-conf/pipeline-settings) or click on*Account settings* on the left sidebar and then choose*Pipeline settings* item on the next screen.

On this page, youcan define global parameters for thewhole Codefresh account regarding pipeline options. Users can still override some of these options for individual pipelines.

Youcan define global parameters forallthepipelines in the account. Users can still override some of these options for individual pipelines.

{% include image.html

lightbox="true"

max-width="80%"

%}

1. In the Codefresh UI, on the toolbar, click the**Settings** icon.

1. From Configuration in the sidebar, select[**Pipeline Settings**](https://g.codefresh.io/account-admin/account-conf/pipeline-settings){:target="\_blank"}.

Here you can define global template behavior. The options are:

* Enable[pipeline templates]({{site.baseurl}}/docs/docs/pipelines/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.

* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/docs/pipelines/pipelines/#creating-new-pipelines).

* Enable[pipeline templates]({{site.baseurl}}/docs/pipelines/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.

* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/pipelines/pipelines/#creating-a-pipeline).

Note that templates are simply normal pipelines “marked” as a template. There is no technical difference between templates and actual pipelines.

Here you can restrict the sources of pipeline YAML that users can select. The options are:

* Enable/Disable the[inline editor]({{site.baseurl}}/docs/docs/pipelines/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS

* Enable/Disable the[inline editor]({{site.baseurl}}/docs/pipelines/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS

* Enable/disable pipeline YAML from connected Git repositories

* Enable/disable pipeline YAML from[external URLs]({{site.baseurl}}/docs/docs/pipelines/pipelines/#loading-codefreshyml-from-version-control)

* Enable/disable pipeline YAML from[external URLs]({{site.baseurl}}/docs/pipelines/pipelines/#loading-codefreshyml-from-version-control)

You need to allow at least one of these options so that users can create new pipelines. We suggest leaving the first option enabled when users are still learning about Codefresh and want to experiment.

The syntax for using the secret is {% raw %}`${{secrets.NAME_IN_CODEFRESH.KEY}}`{% endraw %}.

{% raw %}${{secrets.NAME_IN_CODEFRESH.RESOURCE-NAME@KEY}}{% endraw %}

{%highlight yaml %}{%raw %}${{secrets.NAME_IN_CODEFRESH.RESOURCE-NAME@KEY}}{% endraw %}{% endhighlight %

The previous KEY portion is now made of two parts separated using @, where the left side is the name of the resource in the namespace, and the right side the key in that resource.

To use the secret in your pipeline, you have two options:

You can also use secrets in the GUI screens that support them. Currently you can use secrets in:

* Values in[shared configuration]({{site.baseurl}}/docs/pipelines/shared-configuration/)

* Values in[shared configuration]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/)

* Integration with[cloud storage]({{site.baseurl}}/docs/testing/test-reports/#connecting-your-storage-account)

Where secret integration is supported, click on the lock icon and enable the toggle button. You will get a list of your connected secrets:

[Shared Configuration]({{site.baseurl}}/docs/pipelines/shared-configuration/)

[Git triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/)

[Running pipelines locally]({{site.baseurl}}/docs/pipelines/running-pipelines-locally/)

[DebuggingPipelines]({{site.baseurl}}/docs//yaml-examples/examples/trigger-a-k8s-deployment-from-docker-registry/)

[Debuggingpipelines]({{site.baseurl}}/docs//example-catalog/cd-examples/trigger-a-k8s-deployment-from-docker-registry/)

max-width="65%"

%}

see[Hooks in pipelines]({{site.baseurl}}/docs/pipelines/hooks/).

| Percentage bar| use 0-100 value ending with %| 85%|

| Link| use url| {% raw %}`${{CF_COMMIT_URL}}`{% endraw %}|

You can also use[Expression evaluations]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/#condition-expression-syntax) to set metadata.

You can also use[conditional expressions]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/#condition-expression-syntax) to set metadata.

You can annotate an image as part of its build process and also on post build steps.

{:.text-secondary}

You can annotate an image as part of its build process by declaring the metadata value on the[Build step]({{site.baseurl}}/docs/pipelines/steps/build/):

You can annotate an image as part of its build process by declaring the metadata value on the[`build` step]({{site.baseurl}}/docs/pipelines/steps/build/):

1. The`metadata` attribute

2. The`set` operation

3. An array of key-value metadata

{:.text-secondary}

Any step in the YAML workflow can annotate built images by using[Post-Step Operations]({{site.baseurl}}/docs/pipelines/post-step-operations/).

Any step in the YAML workflow can annotate built images by using[post-step operations]({{site.baseurl}}/docs/pipelines/post-step-operations/).

To annotate a built image, configure any step with:

1. The post-step operation

2. The`metadata` attribute

It is also possible to annotate images with the[Codefresh CLI](https://codefresh-io.github.io/cli/).

It is also possible to annotate images with the[Codefresh CLI](https://codefresh-io.github.io/cli/){:target="\_blank"}.

First find the id of an image that you wish to annotate with the command

Then once you have the ID of the image you can use the[annotate command](https://codefresh-io.github.io/cli/images/annotate-image/) to add extra metadata:

Then once you have the ID of the image you can use the[annotate command](https://codefresh-io.github.io/cli/images/annotate-image/){:target="\_blank"} to add extra metadata:

You can also use the Codefresh CLI to fetch existing metadata from images. It is then very easy to extract and process specific fields with[yq](https://github.com/kislyuk/yq)

You can also use the Codefresh CLI to fetch existing metadata from images. It is then very easy to extract and process specific fields with[yq](https://github.com/kislyuk/yq){:target="\_blank"}.

Here is an example

Here is an example:

[ExternalDockerRegistries]({{site.baseurl}}/docs/docker-registries/external-docker-registries/)

[Accessing a Docker registry from your Kubernetes cluster]({{site.baseurl}}/docs/deploy-to-kubernetes/access-docker-registry-from-kubernetes/)

[Dockerregistries for pipeline integrations]({{site.baseurl}}/docs/integrations/docker-registries/)

[Accessing a Docker registry from your Kubernetes cluster]({{site.baseurl}}/docs/ci-cd-guides/access-docker-registry-from-kubernetes/)

This pipeline will run integration tests during the freestyle step called`my_integration_tests` and at that point a Redis instance will be available at hostname`my-redis-db-host` and port 6379. Note how in this example, the service container is placed at the root of the pipeline (as opposed to inside a specific step). This ensures that the Redis instance is running for[the duration of the pipeline]({{site.baseurl}}/docs/pipelines/service-containers/#running-services-for-the-duration-of-the-pipeline).

The service containers have their own output tab in Codefresh UI

The service containers have their own output tab in Codefresh UI.

{% include image.html

lightbox="true"

max-width="70%"

%}

This makes very easy to reuse compositions that you have already defined for other reasons[intheCodefresh UI](https://codefresh.io/docs/docs/testing/create-composition/).

This makes very easy to[reuse compositions]({{site.baseurl}}/docs/testing/create-composition/) that you have already defined for other reasons in Codefresh.

{% endraw %}

{% endhighlight %}

Note that in this case the`docker-compose.yml` file must mention[specific images](https://docs.docker.com/compose/compose-file/#image) (and not use[build properties](https://docs.docker.com/compose/compose-file/#build)).

Note that in this case the`docker-compose.yml` file must mention[specific images](https://docs.docker.com/compose/compose-file/#image){:target="\_blank"} (and not use[build properties](https://docs.docker.com/compose/compose-file/#build){:target="\_blank"}).

When you launch multiple services in your pipelines, you don't know exactly when they will start. Maybe they will be ready once you expect them, but maybe they take too long to start. For example if you use a MySQL database in your integration tests, your integration tests need to know that the database is actually up before trying to use it.

This is the same issue that is present in[vanilla Docker compose](https://docs.docker.com/compose/startup-order/). You can use solutions such as[wait-for-it](https://github.com/vishnubob/wait-for-it) to overcome this limitation, but Codefresh offers a better way in the form of*service readiness*.

This is the same issue that is present in[vanilla Docker compose](https://docs.docker.com/compose/startup-order/){:target="\_blank"}. You can use solutions such as[wait-for-it](https://github.com/vishnubob/wait-for-it){:target="\_blank"} to overcome this limitation, but Codefresh offers a better way in the form of*service readiness*.

With a readiness block you can guarantee that a sidecar service will be actually up before the pipeline will continue. Here is an example:

*`successThreshold`: Minimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for readiness. Minimum value is 1.

*`failureThreshold`: failureThreshold times before giving up. In case of readiness probe the Pod will be marked Unready. Defaults to 3. Minimum value is 1

If you know already how[Kubernetes readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/) work, then these settings will be very familiar to you.

If you know already how[Kubernetes readiness probes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/){:target="\_blank"} work, then these settings will be very familiar to you.

Here is another example where we use the`pg_isready` command to make sure that a PostgreSQL database is ready to accept connections

before we run the integration tests.

[Unittests]({{site.baseurl}}/docs/testing/unit-tests/)

[Integrationtests]({{site.baseurl}}/docs/testing/integration-tests/)

[Integration test with database]({{site.baseurl}}/docs/example-catalog/ci-examples/integration-tests-with-database/)

[CreatingCompositions]({{site.baseurl}}/docs/on-demand-test-environment/create-composition/)

[Unittesting]({{site.baseurl}}/docs/testing/unit-tests/)

[Integrationtesting]({{site.baseurl}}/docs/testing/integration-tests/)

[Integration test with database]({{site.baseurl}}/docs/example-catalog/ci-examples/integration-tests-with-mysql/)

[Creatingcompositions]({{site.baseurl}}/docs/testing/create-composition/)