-
Notifications
You must be signed in to change notification settings - Fork 463
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/1.1] Prevent EdgeHub from starting without a valid configuration #5515
Conversation
b0f9eb6
to
9c86f5b
Compare
9c86f5b
to
b4707f6
Compare
@@ -56,6 +56,13 @@ public async Task Init(IConfigSource configProvider) | |||
{ | |||
Events.GettingConfig(); | |||
await pullTask; | |||
|
|||
this.currentConfig.Expect<InvalidOperationException>(() => throw new InvalidOperationException( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested text - Cannot start successfully as could not get configuration for EdgeHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the same text that is used in later versions. Should we change those also?
0fb5c4f
to
6ba3c2d
Compare
6ba3c2d
to
09cff60
Compare
Prevent updating local state unless the desired state is parseable.
Arguably less safe, but consistent with later revisions.
More informative than current message.
09cff60
to
6214510
Compare
No merge conflicts. Merged changes are in agent, edgelet, and pipeline configuration, and so should not have any problematic interactions with the changes in this branch.
…tion (Azure#5515) Currently, EdgeHub 1.1 can start without a valid configuration. This PR backports logic introduced in later releases to check that a configuration was pulled successfully, and modifies the configuration pulling task to fail when appropriate. Fixes Azure#5398.
…onfiguration (Azure#5515)" This reverts commit 849e110.
…onfiguration (Azure#5515)" This reverts commit 849e110.
There is still an interdependency between the configuration fetch task and the protocol heads in the nested case. The pertinent PR is #5515. ## Azure IoT Edge PR checklist: This checklist is used to make sure that common guidelines for a pull request are followed. ### General Guidelines and Best Practices - [x] I have read the [contribution guidelines](https://github.com/azure/iotedge#contributing). - [x] Title of the pull request is clear and informative. - [x] Description of the pull request includes a concise summary of the enhancement or bug fix.
Currently, EdgeHub 1.1 can start without a valid configuration. This PR backports logic introduced in later releases to check that a configuration was pulled successfully, and modifies the configuration pulling task to fail when appropriate.
Fixes #5398.