Closed navba-MSFT closed 1 year ago
In todays az iot edge deployment create
command --layered
has the same effect as --no-validation
which is to disable client side json schema validation for $edgeHub and $edgeAgent. The schemas used are for full/base deployments.
In todays az iot edge deployment create command --layered has the same effect as --no-validation which is to disable client side json schema validation for $edgeHub and $edgeAgent. The schemas used are for full/base deployments.
@digimaun Thanks for reviewing. If I understood this correctly, the current description This option is an alias for --no-validation.
is valid ?
In todays az iot edge deployment create command --layered has the same effect as --no-validation which is to disable client side json schema validation for $edgeHub and $edgeAgent. The schemas used are for full/base deployments.
@digimaun Thanks for reviewing. If I understood this correctly, the current description
This option is an alias for --no-validation.
is valid ?
Yea the description is accurate. In short, a layered deployment is determined based on an existing base deployment and the form of the users modulesContent, rather than a service toggle. The edge deployment create command description describes this more. There is history around this, we've talked about potential deprecation of the flag, however it currently remains where we may add some form of layered validation.
The description for the
--layered
parameter, says "This option is an alias for --no-validation." I don't think it is an alias for --no-validation - it seems to have a different operation.https://learn.microsoft.com/en-us/cli/azure/iot/edge/deployment?view=azure-cli-latest
Fixes Azure/azure-cli#26502
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Thank you for contributing to the IoT extension!
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines
Intent for Production
dev
ormain
are of production grade. Corollary to this, any merged contributions to these branches may be deployed in a public release at any given time. By checking this box, you agree and commit to the expected production quality of code.Basic expectations
pytest <project root> -vv
. Please provide evidence in the form of a screenshot showing a succesful run of tests locally OR a link to a test pipeline that has been run against the change-set..pylintrc
and.flake8
rules? Look at the CI scripts for example usage.Azure IoT CLI maintainers reserve the right to enforce any of the outlined expectations.
A PR is considered ready for review when all basic expectations have been met (or do not apply).