Error IO tag for Imperative Errors
Crash if we detect that we are running in team-config mode. You should not be able to operate on old-school profiles when you are in team-config mode. Give a meaningful message as part of our crash.
Extracts the profile name from the file path/name
the file path to extract the profile name
the extension of the file
Accepts the profiles root directory and returns all directories within. The directories within the root directory are all assumed to be profile type directories (potentially containing a meta file and profiles of that type).
The profiles root directory to obtain all profiles from.
Accepts the profile directory location for a type, reads all filenames, and returns a list of profile names that are present within the directory (excluding the meta profile)
The directory for the type
the extension for the profile files (normally YAML)
the meta name for this type
Read the profile meta file using Yaml "safeLoad" (ensures that no code executes, etc. during the load). The meta profile file for a type contains the default profile specification. The meta profile is ALWAYS in YAML format (controlled exclusively by the Imperative framework).
The path to the meta profile
Read a profile from disk. Profiles are always assumed to be YAML (YAML "safeLoad" is invoked to perform the load).
Path to the profile.
The profile type; used to populate the "type" in the profile object (type property not persisted on disk).
Generated using TypeDoc
The V1ProfileRead class is for reading V1 profiles from disk. V1 profiles are not supported as of Zowe V3. Profiles should only be read for the purpose of converting the V1 profiles to a current zowe client configuration. All "fs" calls are wrapped here and errors are transformed to ImperativeError for error handling/flow throughout Imperative.