Skip to content
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

[pack] adding support for IWebJobsConfigurationStartup #5991

Merged
merged 24 commits into from
May 29, 2020
Merged

Conversation

brettsam
Copy link
Member

@brettsam brettsam commented May 5, 2020

No description provided.

fabiocav
fabiocav previously approved these changes May 6, 2020
src/WebJobs.Script/NullHostedService.cs Show resolved Hide resolved
@fabiocav
Copy link
Member

fabiocav commented May 6, 2020

@brettsam any idea on what the impact to cold start/initialization is with these changes?

@safihamid would be good to update the profile to ensure this new code path is optimized.

@brettsam
Copy link
Member Author

brettsam commented May 6, 2020

@safihamid is there an easy way to gather numbers on a build from this PR? I agree that'd be good to look at. Of course the actual real-life numbers may vary as this calls into customer code, but we can make sure that our code isn't doing anything crazy here.

@safihamid
Copy link
Contributor

I will get some profiles with this PR next week.

sb.AppendLine($" Function '{invalidValueMap.Key}' uses the modified key(s): {string.Join(", ", invalidValueMap.Value)}");
}

_logger.LogWarning(new EventId(700, "ConfigurationModifiedInExternalStartup"), sb.ToString());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed, we need to think about a hard failure here if running in consumption. At the very least, we need detectors to ensure it's easy to diagnose when scaling stops working because of potential misconfiguration.

@@ -405,7 +405,7 @@ jobs:
inputs:
command: 'test'
testRunTitle: "C# end to end tests"
arguments: '--filter "Group=CSharpEndToEndTests"'
arguments: '--filter "Group=CSharpEndToEndTests" -v n'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove?

fabiocav
fabiocav previously approved these changes May 28, 2020
@brettsam
Copy link
Member Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@allenzhang83
Copy link

When will this be released to V3?

@brettsam
Copy link
Member Author

brettsam commented Jun 8, 2020

It's all merged in but the release has not been pushed to production yet. I'd expect it to be everywhere in about 2 weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants