> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/use-continuous-delivery/deploy-services-on-different-platforms/tanzu/add-config-files.md).

# Add config files for TAS

Service configuration files enable you to specify information in the Harness service that can be referenced in other parts of the Harness application. In this topic, we'll cover using these configuration files for Tanzu Application Service (TAS, formerly PCF).

{% tabs %}
{% tab title="Harness" %}

1. In the Harness service, in Config Files, select **Add Config File**.
2. In **Config File Source**, select **Harness**, and then select **Continue**.
3. In **Config File Identifier**, enter a name for the file.
4. In **File/Folder Path**, select the config file from Harness file store.

   For more information, go to [add inline service using file store](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/add-inline-manifests-using-file-store.md).
5. Select **Add** to attach multiple files as a single config file.
6. Select **Submit**. ![](/files/vq6WMHaDYH7Or7qKR8wS)

For more information, go to [Use config file in your deployments](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/cd-services-config-files.md).

You can view the config files added to your service definition.

You can reference this config file as an expression in a pipeline from the **Execution** tab.

For example, in a Tanzu Command step, you can reference the config file by entering the following script in the step's **Step Parameters>** **Script>** **Inline**.

`echo "<+configFile.getAsString("shell")>"`
{% endtab %}

{% tab title="GitHub" %}

1. Select a GitHub connector, and select **Continue**. You can also add a [new GitHub connector](/harness-ai/use-harness-platform/connectors/code-repositories/ref-source-repo-provider/git-hub-connector-settings-reference.md) here and reference it.
2. In **Config File Details**, enter a config file name.
3. Enter the name of the repository you want to reference from your GitHub account.
4. In **Git Fetch Type**, select **Latest from Branch**, and then specify the **Branch** name.
5. Enter the file path for config files from GitHub.
6. Select **Add File** to attach multiple files as a single config file.
7. Select **Submit**.

![](/files/rJ0SBzBBqqX9iifqJe2S)

You can view the config files added to your service definition.

You can reference this config file as an expression in a pipeline from the **Execution** tab.

For example, in a Tanzu Command step, you can reference the config file by entering the following script in the step's **Step Parameters>** **Script>** **Inline**.

`echo "<+configFile.getAsString("shellsec")>"`
{% endtab %}
{% endtabs %}