Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
azure-cli-botservice
Advanced tools
This package is for the 'bot service' module. i.e. 'az botservice'
.. :changelog:
0.2.2 +++++
0.2.1 +++++
--lang
parameters for commands0.2.0 +++++
az bot create -v v4 -k webapp
now creates an empty Web App Bot by default (i.e. no bot is deployed to the App Service).
--echo
flag when creating a v4 Web App Bot.v3
bot creation does not support using the --echo
flag.--version
is now v4
, not v3
(except for az bot prepare-publish
).--lang
no longer defaults to Csharp
. If the command requires --lang
and it is not provided, the command will error out.--appid
and --password
args for az bot create
are now required and can be created via az ad app create
.
--appid
and --password
validationsaz bot create -v v4
does not create or use a Storage Account or Application Insights.az bot create -v v3
, the command only accepts regions where Application Insights is creatable.az bot update
is no longer a generic update command, but instead can affect specific properties of a bot.Javascript
instead of Node
. Node
as a --lang
value is no longer supported.az bot create -v v4 -k webapp
no longer sets SCM_DO_BUILD_DURING_DEPLOYMENT
to true. All deployments through Kudu will act according to their default behavior.az bot download
for bots without .bot files now create the language-specific configuration file with values from the Application Settings for the bot.Typescript
support to az bot prepare-deploy
az bot prepare-deploy
for Javascript
and Typescript
bots.
--code-dir
doesn't contain a package.json.az bot prepare-deploy
returns true
if successful and has helpful verbose logging.az bot create -v v3
0.1.10 ++++++
0.1.9 +++++
az bot prepare-deploy
to prepare for deploying bots via az webapp
az bot create --kind registration
show password if the password is not provided--endpoint
in az bot create --kind registration
default empty string instead of being required0.1.8 +++++
az bot publish
command output at end of az bot create
az bot publish
0.1.7 +++++
botservice (0.4.3)
extension, this functionality has been rolled into the core CLI0.1.6 +++++
az bot publish
npm install
during az bot publish
--name
in az bot create
--proj-name
argument for --proj-file-path
--proj-file
messages to instead use --proj-file-path
az bot publish
now removes fetched IIS Node.js deployment files if they did not already exist
--keep-node-modules
to az bot publish
to not delete node_modules folder on App Service"publishCommand"
key-value pair to output from az bot create
when creating an Azure Function or Web App bot.
"publishCommand"
is an az bot publish
command prepopulated with the required parameters to publish the newly created bot."WEBSITE_NODE_DEFAULT_VERSION"
in ARM template for v4 SDK bots to use 10.14.1 instead of 8.9.40.1.5 +++++
0.1.4 +++++
az bot create
0.1.3 +++++
az bot show
0.1.2 +++++
0.1.1 +++++
0.1.0 +++++
FAQs
Microsoft Azure Command-Line Tools Bot Services Command Module
We found that azure-cli-botservice demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.