Skip to main content

Microsoft Azure CLI ‘bot service’ Command Module

This package is for the ‘bot service’ module. i.e. ‘az botservice’

Release History

  • Add “discontinued support”/”maintenance mode”-warning messages for commands that support the v3 SDK

0.2.1

  • Allow all casing for –lang parameters for commands

  • Update description for command module

0.2.0

  • [Breaking Change]: 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).
    • To use the Echo Bot template that was always deployed in the past, use the new –echo flag when creating a v4 Web App Bot.

    • v3 bot creation does not support using the –echo flag.

  • [Breaking Change]: The default value for –version is now v4, not v3 (except for az bot prepare-publish).

  • [Breaking Change]: –lang no longer defaults to Csharp. If the command requires –lang and it is not provided, the command will error out.

  • [Breaking Change]: The –appid and –password args for az bot create are now required and can be created via az ad app create.
    • Add –appid and –password validations

  • [Breaking Change]: az bot create -v v4 does not create or use a Storage Account or Application Insights.

  • [Breaking Change]: Instead of mapping Application Insights regions for az bot create -v v3, the command only accepts regions where Application Insights is creatable.

  • [Breaking Change]: az bot update is no longer a generic update command, but instead can affect specific properties of a bot.

  • [Breaking Change]: All –lang flags now accept Javascript instead of Node. Node as a –lang value is no longer supported.

  • [Breaking Change]: 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.

  • Add Typescript support to az bot prepare-deploy

  • Add warning message to az bot prepare-deploy for Javascript and Typescript bots.
    • This message only appears if the –code-dir doesn’t contain a package.json.

  • az bot prepare-deploy returns true if successful and has helpful verbose logging.

  • Add more available Application Insights regions to az bot create -v v3

0.1.10

  • Minor fixes

0.1.9

  • Add az bot prepare-deploy to prepare for deploying bots via az webapp

  • Have az bot create –kind registration show password if the password is not provided

  • Have –endpoint in az bot create –kind registration default empty string instead of being required

0.1.8

  • Add “SCM_DO_BUILD_DURING_DEPLOYMENT” to ARM template’s Application Settings for v4 Web App Bots

  • Add “Microsoft-BotFramework-AppId” and “Microsoft-BotFramework-AppPassword” to ARM template’s Application Settings for v4 Web App Bots

  • Remove single quotes from az bot publish command output at end of az bot create

  • Use async zipdeploy API for deploying bots via az bot publish

0.1.7

  • Suppress latest botservice (0.4.3) extension, this functionality has been rolled into the core CLI

0.1.6

  • Improve UX around az bot publish

  • Add warning for timeouts when running npm install during az bot publish

  • Remove invalid char “.” from –name in az bot create

  • Stop randomizing resource names when creating Azure Storage, App Service Plan, Function/Web App and Application Insights

  • Code cleanup in BotTemplateDeployer

  • Deprecate –proj-name argument for –proj-file-path

  • Update old –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 * The command does not remove any local IIS Node.js files if detected when command is initiated.

  • Add –keep-node-modules to az bot publish to not delete node_modules folder on App Service

  • Add “publishCommand” key-value pair to output from az bot create when creating an Azure Function or Web App bot. * The value of “publishCommand” is an az bot publish command prepopulated with the required parameters to publish the newly created bot.

  • Update “WEBSITE_NODE_DEFAULT_VERSION” in ARM template for v4 SDK bots to use 10.14.1 instead of 8.9.4

0.1.5

  • Minor fixes

0.1.4

  • Add deployment status updates to az bot create

0.1.3

  • Add support for .bot file parsing when calling az bot show

  • Fix AppInsights provisioning bug

  • Fix whitespace bug when dealing with file paths

  • Reduce Kudu network calls

  • Additional UX improvements

0.1.2

  • Major refactoring

  • Improvements to test coverage

0.1.1

  • Minor fixes

0.1.0

  • Initial Bot Service CLI Release

Metadata

Release files for opal-azure-cli-botservice 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for opal-azure-cli-botservice 0.2.4
File Size Uploaded Provenance
opal-azure-cli-botservice-0.2.4.tar.gz 39.8 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for opal-azure-cli-botservice 0.2.4
File Interpreter ABI Platform
opal_azure_cli_botservice-0.2.4-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 89.9 kB

Release files / opal-azure-cli-botservice-0.2.4.tar.gz

Download URL opal-azure-cli-botservice-0.2.4.tar.gz
Size 39.8 kB
Tags Source
SHA-256 checksum
How to use checksums
efd24802b0fbfd5889c37c0ecf09b197de183bb2ad1d2b866c5fa061477484fb
BLAKE2b-256 checksum
How to use checksums
bed31b9a48a73f7ff6a6568e9337dba3c15e4fcea9448be9cbabf3135f0989fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3

Release files / opal_azure_cli_botservice-0.2.4-py2.py3-none-any.whl

Download URL opal_azure_cli_botservice-0.2.4-py2.py3-none-any.whl
Size 50.1 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
f10bc1d0b2699a8bdbf4b52aeef7e2cc61fc929aefeace5edf64aff5e488483d
BLAKE2b-256 checksum
How to use checksums
15c30daaf15db2f8d2161080a98276aa83f851ec458d09a02bd372f573420384
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3

Security for opal-azure-cli-botservice 0.2.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page