-
Notifications
You must be signed in to change notification settings - Fork 447
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
Add host.json for sync trigger payload #7386
Conversation
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 looks good to me, but let's also get a sign-off from @mathewc
Co-authored-by: Chris Gillum <cgillum@microsoft.com>
// Add host.json to the payload | ||
if (_environment.IsKubernetesManagedHosting()) | ||
{ | ||
result.Add("host.json", GetHostJson()); |
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.
See the comment I left in the previous iteration. Looks like a revision you posted blew the comment away.
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.
Let's not make this Kubernetes specific, since part of our larger goal is to address #7288. Instead, I think we should add just the host.json "extensions" section here, and below if we revert to minimal format based on size, we redefine the minimal format as { triggers: [], extensions: {} }
ensuring this data is present in that case as well.
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.
Thank you @mathewc
Done.
Could you have a look?
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.
Looks good. I just had one more comment that I added on removing the unnecessary log statement. They we can get this checked in after you add a test for the scenario - I believe you're in the process of adding one?
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.
Thank you @mathewc
I tested E2E, so that code is good for now, I'm planning add unit testing for it.
Do we need E2E testing as well? If so I'd happy to do that.
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.
For the scope of the changes here unit test is enough! Thanks!
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.
I added an Unit Test. Looks good?
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.
I don’t see updates to unit tests. Missed a commit?
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.
Hi @pragnagopa
Sorry, I missed. Now added.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @mathewc |
I'm testing this PR E2E once it finished, I'll share it. |
|
||
namespace Microsoft.Azure.WebJobs.Script.Tests.Managment | ||
{ | ||
public class FunctionsSyncManagerTests |
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.
Why did you add a new file for this test - we already have an existing test suite here
azure-functions-host/test/WebJobs.Script.Tests.Integration/Management/FunctionsSyncManagerTests.cs
Line 31 in 6cef580
public class FunctionsSyncManagerTests : IDisposable |
In the upcoming PR, let's fix this. Also, the test doesn't really test the feature/changes you added - ensuring that the actual sync triggers payload contains the expected content.
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.
Under the Kubernetes Environment, We need to
host.json
payload for SyncTrigger scenario for transforming Durable Functions and LogicApp scenario.I currently testing this branch not finished, so that I make it Draft, However, this change should requires discussion with us. I just simply add the
host.json
payload on the current sync trigger payload.CC @pragnagopa , @ahmelsayed
Issue describing the changes in this PR
resolves #7288 #7382
Pull request checklist
release_notes.md