> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/troubleshoot/best-practices/how-to-include-network-settings-in-commit-or-deployment.md).

# How to Include Network Settings in Commit or Deployment

## Overview

This guide outlines the steps to include network settings during a commit or deployment in AutoRABIT. Following these steps ensures that network access configurations are properly managed and deployed.

### Steps to Include Network Settings

1. **Metadata Retrieval in EZ-Commit / Deployment**
   * During the **metadata retrieval stage** of an EZ-Commit or Deployment job, ensure the **`security`** metadata is included under the **`settings`** section.
   * This step ensures that network-related configurations, including IP ranges and login IPs, are captured for commit or deployment.
2. **Compare Changes Stage**
   * In the **Compare Changes** stage, review all **Network Access** changes included in the commit. This is particularly important for **existing commits** (ex commits).
   * Use this stage to validate that all required network settings have been accurately captured.

***

> **Important Note:**\
> For secure and efficient deployments, it is **recommended to grant IP access based on the deployment profile**. This ensures that only the necessary IP ranges are permitted, maintaining both compliance and security standards.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/arm/troubleshoot/best-practices/how-to-include-network-settings-in-commit-or-deployment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.