2019-11-07 21:26:45 +01:00
|
|
|
<?xml version="1.0" encoding="utf-8"?>
|
|
|
|
|
<root>
|
|
|
|
|
<!--
|
|
|
|
|
Microsoft ResX Schema
|
|
|
|
|
|
|
|
|
|
Version 2.0
|
|
|
|
|
|
|
|
|
|
The primary goals of this format is to allow a simple XML format
|
|
|
|
|
that is mostly human readable. The generation and parsing of the
|
|
|
|
|
various data types are done through the TypeConverter classes
|
|
|
|
|
associated with the data types.
|
|
|
|
|
|
|
|
|
|
Example:
|
|
|
|
|
|
|
|
|
|
... ado.net/XML headers & schema ...
|
|
|
|
|
<resheader name="resmimetype">text/microsoft-resx</resheader>
|
|
|
|
|
<resheader name="version">2.0</resheader>
|
|
|
|
|
<resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
|
|
|
|
|
<resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
|
|
|
|
|
<data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
|
|
|
|
|
<data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
|
|
|
|
|
<data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
|
|
|
|
|
<value>[base64 mime encoded serialized .NET Framework object]</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
|
|
|
|
|
<value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
|
|
|
|
|
<comment>This is a comment</comment>
|
|
|
|
|
</data>
|
|
|
|
|
|
|
|
|
|
There are any number of "resheader" rows that contain simple
|
|
|
|
|
name/value pairs.
|
|
|
|
|
|
|
|
|
|
Each data row contains a name, and value. The row also contains a
|
|
|
|
|
type or mimetype. Type corresponds to a .NET class that support
|
|
|
|
|
text/value conversion through the TypeConverter architecture.
|
|
|
|
|
Classes that don't support this are serialized and stored with the
|
|
|
|
|
mimetype set.
|
|
|
|
|
|
|
|
|
|
The mimetype is used for serialized objects, and tells the
|
|
|
|
|
ResXResourceReader how to depersist the object. This is currently not
|
|
|
|
|
extensible. For a given mimetype the value must be set accordingly:
|
|
|
|
|
|
|
|
|
|
Note - application/x-microsoft.net.object.binary.base64 is the format
|
|
|
|
|
that the ResXResourceWriter will generate, however the reader can
|
|
|
|
|
read any of the formats listed below.
|
|
|
|
|
|
|
|
|
|
mimetype: application/x-microsoft.net.object.binary.base64
|
|
|
|
|
value : The object must be serialized with
|
|
|
|
|
: System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
|
|
|
|
|
: and then encoded with base64 encoding.
|
|
|
|
|
|
|
|
|
|
mimetype: application/x-microsoft.net.object.soap.base64
|
|
|
|
|
value : The object must be serialized with
|
|
|
|
|
: System.Runtime.Serialization.Formatters.Soap.SoapFormatter
|
|
|
|
|
: and then encoded with base64 encoding.
|
|
|
|
|
|
|
|
|
|
mimetype: application/x-microsoft.net.object.bytearray.base64
|
|
|
|
|
value : The object must be serialized into a byte array
|
|
|
|
|
: using a System.ComponentModel.TypeConverter
|
|
|
|
|
: and then encoded with base64 encoding.
|
|
|
|
|
-->
|
|
|
|
|
<xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
|
|
|
|
|
<xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
|
|
|
|
|
<xsd:element name="root" msdata:IsDataSet="true">
|
|
|
|
|
<xsd:complexType>
|
|
|
|
|
<xsd:choice maxOccurs="unbounded">
|
|
|
|
|
<xsd:element name="metadata">
|
|
|
|
|
<xsd:complexType>
|
|
|
|
|
<xsd:sequence>
|
|
|
|
|
<xsd:element name="value" type="xsd:string" minOccurs="0" />
|
|
|
|
|
</xsd:sequence>
|
|
|
|
|
<xsd:attribute name="name" use="required" type="xsd:string" />
|
|
|
|
|
<xsd:attribute name="type" type="xsd:string" />
|
|
|
|
|
<xsd:attribute name="mimetype" type="xsd:string" />
|
|
|
|
|
<xsd:attribute ref="xml:space" />
|
|
|
|
|
</xsd:complexType>
|
|
|
|
|
</xsd:element>
|
|
|
|
|
<xsd:element name="assembly">
|
|
|
|
|
<xsd:complexType>
|
|
|
|
|
<xsd:attribute name="alias" type="xsd:string" />
|
|
|
|
|
<xsd:attribute name="name" type="xsd:string" />
|
|
|
|
|
</xsd:complexType>
|
|
|
|
|
</xsd:element>
|
|
|
|
|
<xsd:element name="data">
|
|
|
|
|
<xsd:complexType>
|
|
|
|
|
<xsd:sequence>
|
|
|
|
|
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
|
|
|
|
|
<xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
|
|
|
|
|
</xsd:sequence>
|
|
|
|
|
<xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
|
|
|
|
|
<xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
|
|
|
|
|
<xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
|
|
|
|
|
<xsd:attribute ref="xml:space" />
|
|
|
|
|
</xsd:complexType>
|
|
|
|
|
</xsd:element>
|
|
|
|
|
<xsd:element name="resheader">
|
|
|
|
|
<xsd:complexType>
|
|
|
|
|
<xsd:sequence>
|
|
|
|
|
<xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
|
|
|
|
|
</xsd:sequence>
|
|
|
|
|
<xsd:attribute name="name" type="xsd:string" use="required" />
|
|
|
|
|
</xsd:complexType>
|
|
|
|
|
</xsd:element>
|
|
|
|
|
</xsd:choice>
|
|
|
|
|
</xsd:complexType>
|
|
|
|
|
</xsd:element>
|
|
|
|
|
</xsd:schema>
|
|
|
|
|
<resheader name="resmimetype">
|
|
|
|
|
<value>text/microsoft-resx</value>
|
|
|
|
|
</resheader>
|
|
|
|
|
<resheader name="version">
|
|
|
|
|
<value>2.0</value>
|
|
|
|
|
</resheader>
|
|
|
|
|
<resheader name="reader">
|
|
|
|
|
<value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
|
|
|
|
</resheader>
|
|
|
|
|
<resheader name="writer">
|
|
|
|
|
<value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
|
|
|
|
|
</resheader>
|
|
|
|
|
<data name="AzureCodeExpiry" xml:space="preserve">
|
|
|
|
|
<value>This code will expire in 15 minutes.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureEnterTenant" xml:space="preserve">
|
|
|
|
|
<value>Please enter the desired tenant number.</value>
|
|
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureNewLogin" xml:space="default">
|
|
|
|
|
<value>Enter %s to login with a different account</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureRemoveStored" xml:space="default">
|
|
|
|
|
<value>Enter %s to remove the above saved connection settings.</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureInvalidAccessInput" xml:space="default">
|
|
|
|
|
<value>Please enter a valid number to access the stored connection settings, %s to make a new one, or %s to remove the stored ones.</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
|
|
|
|
<data name="AzureNonNumberError" xml:space="preserve">
|
|
|
|
|
<value>Please enter a number.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureNumOutOfBoundsError" xml:space="preserve">
|
|
|
|
|
<value>Number out of bounds. Please enter a valid number.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureNoTenants" xml:space="preserve">
|
|
|
|
|
<value>Could not find any tenants.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureNoCloudAccount" xml:space="preserve">
|
|
|
|
|
<value>You have not set up your cloud shell account yet. Please go to https://shell.azure.com to set it up.</value>
|
|
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureStorePrompt" xml:space="default">
|
|
|
|
|
<value>Do you want to save these connection settings for future logins? [%s/%s]</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureInvalidStoreInput" xml:space="default">
|
|
|
|
|
<value>Please enter %s or %s</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
|
|
|
|
<data name="AzureRequestingCloud" xml:space="preserve">
|
|
|
|
|
<value>Requesting a cloud shell instance...</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureSuccess" xml:space="preserve">
|
|
|
|
|
<value>Succeeded.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureRequestingTerminal" xml:space="preserve">
|
|
|
|
|
<value>Requesting a terminal (this might take a while)...</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureTokensStored" xml:space="preserve">
|
|
|
|
|
<value>Your connection settings have been saved for future logins.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureNoTokens" xml:space="preserve">
|
|
|
|
|
<value>No tokens to remove.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureTokensRemoved" xml:space="preserve">
|
|
|
|
|
<value>Saved connection settings removed.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureExitStr" xml:space="preserve">
|
|
|
|
|
<value>Exit.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureAuthString" xml:space="preserve">
|
|
|
|
|
<value>Authenticated.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureInternetOrServerIssue" xml:space="preserve">
|
|
|
|
|
<value>Could not connect to Azure. You may not have internet or the server might be down.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureOldCredentialsFlushedMessage" xml:space="preserve">
|
|
|
|
|
<value>Authentication parameters changed. You'll need to log in again.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureUnknownTenantName" xml:space="preserve">
|
|
|
|
|
<value><unknown tenant name></value>
|
|
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
<data name="AzureIthTenant" xml:space="default">
|
|
|
|
|
<value>Tenant %s: %s (%s)</value>
|
2019-11-07 21:26:45 +01:00
|
|
|
</data>
|
|
|
|
|
<data name="AzureSuccessfullyAuthenticated" xml:space="preserve">
|
|
|
|
|
<value>Authenticated.</value>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureUserEntry_NewLogin" xml:space="preserve">
|
|
|
|
|
<value>n</value>
|
|
|
|
|
<comment>The user must enter this character to say NEW LOGIN (AzureInvalidAccessInput, AzureNewLogin)</comment>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureUserEntry_RemoveStored" xml:space="preserve">
|
|
|
|
|
<value>r</value>
|
|
|
|
|
<comment>The user must enter this character to say REMOVE SAVED LOGINS (AzureRemoveStored, AzureInvalidAccessInput)</comment>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureUserEntry_Yes" xml:space="preserve">
|
|
|
|
|
<value>y</value>
|
|
|
|
|
<comment>The user must enter this character to signify YES</comment>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="AzureUserEntry_No" xml:space="preserve">
|
|
|
|
|
<value>n</value>
|
|
|
|
|
<comment>The user must enter this character to signify NO</comment>
|
|
|
|
|
</data>
|
2019-11-25 23:22:29 +01:00
|
|
|
<data name="ProcessExited" xml:space="preserve">
|
|
|
|
|
<value>[process exited with code %u]</value>
|
|
|
|
|
<comment>The first argument (%u) is the (positive) error code of the process. 0 is success.</comment>
|
|
|
|
|
</data>
|
|
|
|
|
<data name="ProcessFailedToLaunch" xml:space="preserve">
|
|
|
|
|
<value>[error 0x%8.08x when launching `%ls']</value>
|
|
|
|
|
<comment>The first argument is the hexadecimal error code. The second is the process name.
|
|
|
|
|
If this resource spans multiple lines, it will not be displayed properly. Yeah.</comment>
|
|
|
|
|
</data>
|
2019-12-09 20:07:08 +01:00
|
|
|
<data name="TelnetInternetOrServerIssue" xml:space="preserve">
|
|
|
|
|
<value>Could not connect to telnet server.</value>
|
|
|
|
|
</data>
|
AzCon: improve input, usability, reliability (4 commits) (#4756)
* Azure: rewrite user input handler
This commit replaces the AzureConnection's input handler with one that
acts more like "getline()". Instead of the Read thread setting a state
and WriteInput filling in the right member variable, the reader blocks
on the user's input and receives it in an optional<string>.
This moves the input number parsing and error case handling closer to
the point where those inputs are used, as opposed to where they're
collected.
It also switches our input to be "line-based", which is a huge boon for
typing tenant numbers >9. This fixes #3233. A simple line editor
(supporting only backspace and CR) is included.
It also enables echo on user input, and prints it in a nice pretty green
color.
It also enables input queueing: if the user types anything before the
connection is established, it'll be sent once it is.
Fixes #3233.
* Azure: display the user's options and additional information in color
This commit colorizes parts of the AzCon's strings that include "user
options" -- things the user can type -- in yellow. This is to help with
accessibility.
The implementation here is based on a discussion with the team.
Alternative options for coloration were investigated, such as:
* Embedding escape sequences in the resource file.
This would have been confusing for translators.
The RESW file format doesn't support  escapes, so we would need
some magic post-processing.
* Embedding "markup" in the resource file (like #{93m}, ...)
This still would have been annoying for translators.
We settled on an implementation that takes resource names, colorizes
them, and string-formats them into other resources.
* Azure: follow the user's shell choice from the online portal
Fixes #2266.
* Azure: remove all credentials instead of just the first one
2020-03-04 20:30:20 +01:00
|
|
|
</root>
|
