Example: Connecting to GitHub over HTTPS įor best results, create a new empty repo, with no readme file and no commit history. The example below shows a token-based HTTPS connection to GitHub. Connecting to a Remote with a Personal Access Token over HTTPS (Recommended) Ĭribl recommends connecting to a remote repo over HTTPS. Ensure that this repo is secured appropriately. These will be pushed to the remote repo as part of the entire directory structure under version control. Some files that are used by Cribl Stream (both Leader and Worker Groups) contain sensitive keys examples are cret and. Pending commits have a red dot indicator, as shown below. You can also commit changes interactively, using Cribl Stream's UI. Once Git is installed, you can commit configuration changes using the git CLI. Licensing Dashboard Įven on single-instance deployments, the Monitoring > Licensing dashboard will display configuration change markers only if you have git installed. The Leader notifies Workers that a new configuration is available, and Workers pull the new configuration from the Leader Node. Distributed Deployments įor distributed deployments, git must be installed and available locally on the host running the Leader Node.Īll configuration changes must be committed before they are deployed. Git is a hard requirement for certain Cribl Stream features. If you don't have git installed, see the installation links here. The minimum version that Cribl Stream requires is: 1.8.3.1. Git Installation (Local or Standalone/Single-Instance) Cribl.Cloud deployments do not currently support integration with external Git clients or remote repos.
0 kommentar(er)
