Prepare for release 1.1.0 #4342
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
micahl
suggested changes
Feb 4, 2021
varunpuranik
reviewed
Feb 4, 2021
CHANGELOG.md
Outdated
|
|
||
| ## Edge Hub | ||
| ### Changes | ||
| * **Edge Hub will now default to using scope-only authentication for leaf devices**. Prior to this release, the default was to try scope auth, but fall back to cloud auth. Because of this change, users must either (1) [establish a parent/child relationship](https://docs.microsoft.com/en-us/azure/iot-edge/offline-capabilities?view=iotedge-2018-06#set-up-parent-and-child-devices) between the edge device and leaf devices (recommended), or (2) change the default back to its previous value (i.e., set Edge Hub's "AuthenticationMode" environment variable to "CloudAndScope"). |
There was a problem hiding this comment.
@ebertrams and @kgremban to help with the wording here.
My suggestion:
Edge Hub allows only child devices to connect by default
To connect a leaf device to the Edge Hub, users must establish a parent/child relationship between the edge device and the leaf device. For previous versions, this was required only for offline scenarios, as for online scenarios Edge Hub would fall back to cloud based authentication for leaf devices that were not children of the edge device. You can configure Edge Hub to go back to the previous behavior by setting the environment variable "AuthenticationMode" to the value "CloudAndScope".
There was a problem hiding this comment.
Updated. @ebertrams @kgremban what do you think?
varunpuranik
reviewed
Feb 4, 2021
CHANGELOG.md
Outdated
|
|
||
| ## Edge Hub | ||
| ### Changes | ||
| * **Edge Hub allows only child devices to connect by default**. To connect a leaf device to the Edge Hub, users must [establish a parent/child relationship](https://docs.microsoft.com/en-us/azure/iot-edge/offline-capabilities?view=iotedge-2018-06#set-up-parent-and-child-devices) between the edge device and the leaf device. In previous versions, this was required only for offline scenarios, as for online scenarios Edge Hub would fall back to cloud-based authentication for leaf devices that were not children of the edge device. You can configure Edge Hub to go back to the previous behavior by setting the environment variable "AuthenticationMode" to the value "CloudAndScope". |
There was a problem hiding this comment.
@ebertrams / @kgremban - can you pls help check the wording of this? This is imp as it is a breaking change.
varunpuranik
reviewed
Feb 4, 2021
Co-authored-by: Varun Puranik <vpuranik@microsoft.com>
micahl
previously approved these changes
Feb 4, 2021
varunpuranik
previously approved these changes
Feb 4, 2021
yophilav
approved these changes
Feb 6, 2021
darobs
pushed a commit
to darobs/iotedge
that referenced
this pull request
Feb 13, 2021
darobs
pushed a commit
to darobs/iotedge
that referenced
this pull request
Mar 3, 2021
darobs
added a commit
that referenced
this pull request
Mar 3, 2021
* Fix GetModules call error using RFC3339 DateTime format. (#4293) Fix issue calling GetModuleLogs using DirectMethod with a payload that contains parameters using RF3339 DateTime format. * Prepare for release 1.1.0 (#4342) * Update nuget config per security recommendations (#4289) * Set IOTEDGE_HOST before 'make install' (#4396) After commit a34e0ed, the iotedge CLI fails in Mariner because IOTEDGE_HOST was not set during compilation, so the CLI has the wrong path to iotedged's management endpoint. To fix this, we set IOTEDGE_HOST prior to running `make install`. It was already being set prior to `make release`. * Update Base Images for Security Vulnerability 3.1.12 (#4380) - Update ARM32/ARM64 Bionic base images to 3.1.12 - Update AMD64 (Linux) Alpine base images to 3.1.12 - Update AMD64 (Windows) Nanoserver base images to 3.1.12 * Update release 1.1.0 (#4399) Update the CHANGELOG to include the latest commits. * Config yaml 1.1 (#4434) This change updates the default agent tag in config.yaml to 1.1. Cherry-pick a4faab5 and update 1.1-specific Windows config.yaml. * Upgrade sysinfo package (#4444) This change upgrades the sysinfo package in the iotedge CLI and iotedged. It fixes bugs called out in #2747 and #3746. This change was fixed in master earlier and was supposed to by ported to the 1.1 branch, but never was. * EFLOW: Introduce environment variables for nuget operations (#4499) Set env variables to direct nuget caches to the data partition instead of to the rootfs Co-authored-by: Pedro Marcelo Zara <pmzara@hotmail.com> Co-authored-by: Damon Barry <damonbarry@users.noreply.github.com> Co-authored-by: yophilav <54859653+yophilav@users.noreply.github.com> Co-authored-by: ms-mahuber <60939654+ms-mahuber@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.