<commit_before># cloud foundry mgmt
Go automation for managing orgs, spaces that can be driven from concourse pipeline and GIT managed metadata

## Install
Either download a compiled release for your platform (make sure on linux/mac you chmod +x the binary)

**or**

```
go get github.com/pivotalservices/cf-mgmt
```

## Contributing
PRs are always welcome or open issues if you are experiencing an issue and will do my best to address issues in timely fashion.

### The following operation are enabled with cf-mgmt for helping to manage your configuration

#### init-config

This command will initialize a folder structure to add a ldad.yml and orgs.yml file.  This should be where you start to leverage cf-mgmt.  If your foundation is ldap enabled you can specify the ldap configuration info in ldap.yml otherwise you can disable this feature by setting the flag to false.

```
USAGE:
   cf-mgmt init-config [command options] [arguments...]

DESCRIPTION:
   initializes folder structure for configuration

OPTIONS:
   --config-dir value  config dir.  Default is config [$CONFIG_DIR]
```

#### add-org-to-config

This will add the specified org to orgs.yml and create folder based on the org name you specified.  Within this folder will be an orgConfig.yml and spaces.yml which will be empty but will eventually contain a list of spaces.  Any org listed in orgs.yml will be created when the create-orgs operation is ran.

orgConfig.yml allows specifying for the following:
- what groups to map to org roles (OrgManager, OrgBillingManager, OrgAuditor)
- setting up quotas for the org

```
USAGE:
   cf-mgmt add-org-to-config [command options] [arguments...]

DESCRIPTION:<commit_msg>spelling<commit_after># cloud foundry mgmt
Go automation for managing orgs, spaces that can be driven from concourse pipeline and GIT managed metadata

## Install
Either download a compiled release for your platform (make sure on linux/mac you chmod +x the binary)

**or**

```
go get github.com/pivotalservices/cf-mgmt
```

## Contributing
PRs are always welcome or open issues if you are experiencing an issue and will do my best to address issues in timely fashion.

### The following operation are enabled with cf-mgmt for helping to manage your configuration

#### init-config

This command will initialize a folder structure to add a ldap.yml and orgs.yml file.  This should be where you start to leverage cf-mgmt.  If your foundation is ldap enabled you can specify the ldap configuration info in ldap.yml otherwise you can disable this feature by setting the flag to false.

```
USAGE:
   cf-mgmt init-config [command options] [arguments...]

DESCRIPTION:
   initializes folder structure for configuration

OPTIONS:
   --config-dir value  config dir.  Default is config [$CONFIG_DIR]
```

#### add-org-to-config

This will add the specified org to orgs.yml and create folder based on the org name you specified.  Within this folder will be an orgConfig.yml and spaces.yml which will be empty but will eventually contain a list of spaces.  Any org listed in orgs.yml will be created when the create-orgs operation is ran.

orgConfig.yml allows specifying for the following:
- what groups to map to org roles (OrgManager, OrgBillingManager, OrgAuditor)
- setting up quotas for the org

```
USAGE:
   cf-mgmt add-org-to-config [command options] [arguments...]

DESCRIPTION:
{'fraction_non_alphanumeric': 0.06426658732520084, 'fraction_numerical': 0.0, 'mean_word_length': 4.164362519201229, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1477888', 'n_tokens_mistral': 933, 'n_tokens_neox': 889, 'n_words': 471}