ent profile edits

vuepress/docs/next/docs/getting-started/ent-profile.md

@@ -1,3 +1,92 @@
 ---
 sidebarDepth: 1
 ---
+
+
+# Profile Management
+
+The [Entando CLI](entando-cli.md) can define a collection of configuration variables to fully describe an Entando instance. One or more profiles can be created to store configuration settings for a particular instance. The `ent profile` command is available to manage and switch between the configurations of different Entando instances. Refer to `ent profile first-use-readme` for additional details. A profile with this information is automatically generated for a quickstart application.
+
+At minimum, a configuration must consist of the key-value pairs specifying the application name and namespace. To run the application, the Kubernetes connection must also be provided. Cloud Kubernetes tools typically create a Kube context, which can be linked to an Entando profile. An overview of the current connection and profile information is provided via `ent status`.
+
+The following commands perform common operations associated with profile management.
+
+## New Profile
+
+Create and switch to a new profile:
+```
+ent pro new [profileName] [EntandoAppName] [namespace]
+```
+This sets the minimal profile data and outputs next steps.
+
+## Link Profile
+
+Link the current profile to a Kubernetes context (alias of `ent attach-kubectx`):
+```
+ent pro link [contextName]
+```
+This provides ent with instructions to connect to the Kubernetes containing the Entando Application.
+
+## Global Profile
+
+Activate the profile that ent should use across shells:
+```
+ent pro use [profileName]
+```
+This initializes the profile ent should use by default.
+
+## Local Profile
+
+Activate the profile that ent should use within the current shell:
+```
+source ent pro use [profileName]
+```
+
+This allows ent instances in different shells to simultaneously use different Kube contexts, kubeconfigs or custom commands. The quickstart script creates a profile named "qs--{vmname}" that is associated with the Entando Application it generates. 
+## Print
+
+Print a list of the available profiles:
+```
+ent pro list
+```
+
+## Delete
+
+Delete a profile:
+```
+ent pro delete [profileName]
+```
+
+### Configuration Management
+The output of `ent config` is a key-value archive of configuration settings related to the current profile.
+It can serve several purposes, but a few useful commands and keys are listed below.
+
+#### Commands
+Print the current config archive:
+```
+ent config --print
+```
+Interactively edit a config archive:
+```
+ent config --edit
+```
+Return the value of a config key:
+```
+ent config --get {key}
+```
+Set the value of a config key:
+```
+ent config --set {key} {value}
+```
+Delete a config key:
+```
+ent config --set {key}
+```
+#### Keys
+| Key  | Definition  |
+|---|---|
+| ENTANDO_NAMESPACE  |  stores the fallback namespace used by explicit or implicit runs of `ent kubectl` |
+| ENTANDO_APPNAME | stores the Entando Application name related to the current profile |
+| DESIGNATED_JAVA_HOME | stores the path of the Java version used internally by ent |
+
+