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

Empty datastream overrides are no longer sent to the Edge Network, reducing potential conflicts with server side routing configurations #1199

Merged
merged 3 commits into from
Oct 28, 2024

Conversation

ninaceban
Copy link
Contributor

Description

Related Issue

Motivation and Context

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (non-breaking change which does not add functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA or I'm an Adobe employee.
  • I have made any necessary test changes and all tests pass.
  • I have run the Sandbox successfully.

Copy link
Contributor

@carterworks carterworks left a comment

Choose a reason for hiding this comment

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

Excellent.

Should we also check to see if globalEdgeConfigOverrides is empty, like

if (globalEdgeConfigOverrides && !isEmptyObject(globalEdgeConfigOverrides))

?

@ninaceban
Copy link
Contributor Author

Excellent.

Should we also check to see if globalEdgeConfigOverrides is empty, like

if (globalEdgeConfigOverrides && !isEmptyObject(globalEdgeConfigOverrides))

?

Yes, good call, we can add an extra check for localEdgeConfigOverrides, for globalEdgeConfigOverrides I don't see somewhere in the code that we initialize it with empty object, unless the validator does that.

@ninaceban
Copy link
Contributor Author

if (globalEdgeConfigOverrides && !isEmptyObject(globalEdgeConfigOverrides))

Excellent.
Should we also check to see if globalEdgeConfigOverrides is empty, like
if (globalEdgeConfigOverrides && !isEmptyObject(globalEdgeConfigOverrides))
?

Yes, good call, we can add an extra check for localEdgeConfigOverrides, for globalEdgeConfigOverrides I don't see somewhere in the code that we initialize it with empty object, unless the validator does that.

Excellent.
Should we also check to see if globalEdgeConfigOverrides is empty, like
if (globalEdgeConfigOverrides && !isEmptyObject(globalEdgeConfigOverrides))
?

Yes, good call, we can add an extra check for localEdgeConfigOverrides, for globalEdgeConfigOverrides I don't see somewhere in the code that we initialize it with empty object, unless the validator does that.
Carter, thank you, I have added those checks for both, these might come as empty object from the customer.

@jonsnyder jonsnyder merged commit 7c9c6ac into main Oct 28, 2024
4 of 5 checks passed
@jonsnyder jonsnyder deleted the config-overrides branch October 28, 2024 15:20
@jonsnyder jonsnyder changed the title PLATIR-44580 - Do not send empty meta.configOverrides as it invalidates server side config overrides Empty datastream overrides are no longer sent to the Edge Network, reducing potential conflicts with server side routing configurations Oct 31, 2024
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