Skip to content

Removed shim publisher dependence on global flag/setting #1343

Merged
helsaawy merged 1 commit intomicrosoft:masterfrom
helsaawy:he/publisher
Apr 15, 2022
Merged

Removed shim publisher dependence on global flag/setting #1343
helsaawy merged 1 commit intomicrosoft:masterfrom
helsaawy:he/publisher

Conversation

@helsaawy
Copy link
Copy Markdown
Contributor

@helsaawy helsaawy commented Apr 4, 2022

Shim eventPublisher now uses an internal setting for the namespace instead of relying on a global flag.

Signed-off-by: Hamza El-Saawy hamzaelsaawy@microsoft.com

Signed-off-by: Hamza El-Saawy <hamzaelsaawy@microsoft.com>
@helsaawy helsaawy requested a review from a team as a code owner April 4, 2022 21:14
@dcantah dcantah mentioned this pull request Apr 4, 2022
Copy link
Copy Markdown

@katiewasnothere katiewasnothere left a comment

Choose a reason for hiding this comment

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

LGTM

@jterry75
Copy link
Copy Markdown
Contributor

Why did CRI not hit this before since its all in custom namespaces? I'm surprised the events ever worked globally. Were they just matching any global event by type id?

@helsaawy
Copy link
Copy Markdown
Contributor Author

Why did CRI not hit this before since its all in custom namespaces? I'm surprised the events ever worked globally. Were they just matching any global event by type id?

This (should?) have worked properly originally, its just that we were reading a global flag every time we published, which seemed bad.

@helsaawy helsaawy merged commit 2baf93b into microsoft:master Apr 15, 2022
@helsaawy helsaawy deleted the he/publisher branch April 15, 2022 16:25
@jterry75
Copy link
Copy Markdown
Contributor

Oh lol. Misread the code. Yes I see that now, good fix

anmaxvl added a commit that referenced this pull request Feb 7, 2023
Sync ADO with upstream to enable including test GCS binaries as
part of dev-pipeline

Related work items: #1311, #1322, #1341, #1343, #1345, #1347, #1348, #1350, #1353, #1354, #1355, #1358, #1361, #1365, #1368, #1369, #1370
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