The meta profile is saved in each of the profile "type" directories under the profile manager root directory. The meta profile is always named "_meta" and is always stored in YAML format. The contents contain the default profile for the type AND the configuration document for the type. The configuration document is persisted to allow external callers of the Profile Manager APIs (outside of an Imperative init'd environment) to load/save profiles (useful for programmatic invocation from editor plugins, such as VS Code).

export
interface

  IMetaProfile

### Type parameters

- #### T: IProfileTypeConfiguration

### Hierarchy

- IMetaProfile

## Index

### Properties

- configuration
- defaultProfile

## Properties

### configuration

configuration: T

- Defined in @zowe/imperative/src/profiles/src/doc/definition/IMetaProfile.ts:37

The Configuration Document supplied for this type.

memberof

  IMetaProfile

### defaultProfile

defaultProfile: string

- Defined in @zowe/imperative/src/profiles/src/doc/definition/IMetaProfile.ts:31

The default profile for the "type" - this profile will be loaded by the manager if the default is requested. This is a convience for users of the CLI (and programmatic invocation) to avoid having to supply a profile name for the type. You can also set the default using the Profile Manager APIs.

memberof

  IMetaProfile

Generated using TypeDoc