Developer-user-manager Save-user

Create a new developer user in the local files

beam developer-user-manager save-user [options]

About

Create a new developer user in the local files

Options

NameTypeDescription
--aliasIEnumerable`1A alias (Name) of the user, which is not the same name as in the portal
--descriptionIEnumerable`1A new description for this user
--user-typeInt32The user type of the user
--pidIEnumerable`1The PID of the user
--cidIEnumerable`1The CID of the user
--gamer-tagIEnumerable`1The Gamer Tag of the user
--access-tokenIEnumerable`1The access token to be saved
--refresh-tokenIEnumerable`1The refresh token to be saved
--expires-inIEnumerable`1The expires to be saved
--tagsIEnumerable`1The tags to set in the local user data splited by @@
--dryrunBoolean[DEPRECATED] Run as much of the command as possible without making any network calls
--cidStringCID (CustomerId) to use (found in Portal->Account); defaults to whatever is in '.beamable/connection-configuration.json'
--engineStringIf passed, sets the engine integration that is calling for the command
--engine-sdk-versionStringThe version of the Beamable's SDK running in that Engine
--engine-versionStringThe version of the engine that is calling the CLI
--pidStringPID (Realm ID) to use (found in Portal -> Games -> Any Realm's details); defaults to whatever is in '.beamable/connection-configuration.json'
--quietBooleanWhen true, skip input waiting and use default arguments (or error if no defaults are possible)
--hostStringThis option defines the target Beamable environment. Needed for private cloud customers to target their exclusive Beamable environment. Ignorable by everyone else. Stored in '.beamable/connection-configuration.json'
--access-tokenStringThe access token to use for the requests. It overwrites the logged in user stored in connection-auth.json for THIS INVOCATION ONLY
--refresh-tokenStringA Refresh Token to use for the requests. It overwrites the logged in user stored in connection-auth.json for THIS INVOCATION ONLY
--logStringExtra logs gets printed out
--no-redirectBooleanIf there is a local dotnet tool installation (with a ./config/dotnet-tools.json file) for the beam tool, then any global invocation of the beam tool will automatically redirect and call the local version. However, there will be a performance penalty due to the extra process invocation. This option flag will cause an error to occur instead of automatically redirecting the execution to a new process invocation.
--prefer-remote-federationBooleanBy default, any local CLI invocation that should trigger a Federation of any type will prefer locally running Microservices. However, if you need the CLI to use the remotely running Microservices, use this option to ignore locally running services.
--unmask-logsBooleanBy default, logs will automatically mask tokens. However, when this option is enabled, tokens will be visible in their full text. This is a security risk.
--no-log-fileBooleanBy default, logs are automatically written to a temp file so that they can be used in an error case. However, when this option is enabled, logs are not written. Also, if the BEAM_CLI_NO_FILE_LOG environment variable is set, no log file will be written.
--docker-cli-pathStringa custom location for docker. By default, the CLI will attempt to resolve docker through its usual install locations. You can also use the BEAM_DOCKER_EXE environment variable to specify.
Currently, a docker path has been automatically identified.
--emit-log-streamsBooleanOut all log messages as data payloads in addition to however they are logged
--add-project-pathIEnumerable`1additional file paths to be included when building a local project manifest.
--dirString[DEPRECATED] Path override for the .beamable folder
--rawBooleanOutput raw JSON to standard out. This happens by default when the command is being piped
--prettyBooleanOutput syntax highlighted box text. This happens by default when the command is not piped
--dotnet-pathStringa custom location for dotnet
--versionBooleanShow version information
--helpBooleanShow help and usage information

Parent Command

developer-user-manager