Skip to content

Remove sequential route blocks from traffic splitting#445

Merged
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
amalgam8:update_traffic_docs
Feb 8, 2017
Merged

Remove sequential route blocks from traffic splitting#445
mattklein123 merged 1 commit intoenvoyproxy:masterfrom
amalgam8:update_traffic_docs

Conversation

@rshriram
Copy link
Copy Markdown
Member

@rshriram rshriram commented Feb 8, 2017

The current docs describe how to achieve traffic splitting in two ways: weighted_clusters and using sequential route blocks (duplicate entries, except for runtime values). The latter has proven to be very confusing. This PR removes documentation associated with the latter.

@mattklein123 mattklein123 merged commit a5b6943 into envoyproxy:master Feb 8, 2017
@rshriram rshriram deleted the update_traffic_docs branch March 23, 2017 15:30
jpsim pushed a commit that referenced this pull request Nov 28, 2022
Description: this is a follow up to #498. This PR introduces `envoy_engine_callbacks`. They are similar in nature to envoy_http_callbacks. The difference being that they are not exposed all the way to consumer level in the library as it is not needed right now. However, one can see how by adding a type erased context pointer, and following the platform patterns for http callbacks we could thread this all the way up if need be. The immediate need for these callbacks is to detach the engine's native thread from the JVM on Android.
Risk Level: med -- adds complexity to engine management.
Testing: local testing on devices (Lyft and example app on iOS and Android).

In conjunction with #498 this PR Fixes #492 #445

Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: JP Simard <jp@jpsim.com>
jpsim pushed a commit that referenced this pull request Nov 29, 2022
Description: this is a follow up to #498. This PR introduces `envoy_engine_callbacks`. They are similar in nature to envoy_http_callbacks. The difference being that they are not exposed all the way to consumer level in the library as it is not needed right now. However, one can see how by adding a type erased context pointer, and following the platform patterns for http callbacks we could thread this all the way up if need be. The immediate need for these callbacks is to detach the engine's native thread from the JVM on Android.
Risk Level: med -- adds complexity to engine management.
Testing: local testing on devices (Lyft and example app on iOS and Android).

In conjunction with #498 this PR Fixes #492 #445

Signed-off-by: Jose Nino <jnino@lyft.com>
Signed-off-by: JP Simard <jp@jpsim.com>
mathetake pushed a commit that referenced this pull request Mar 3, 2026
**Commit Message**

- Implement Azure OpenAI integration including a) backend auth handler
b) Azure token rotator.
- Replace oauth package with `token_provider` to simplify AWS and Azure
token request logic.
- Fix existing test case i.e. in backendsecurity_test.go when oidc is
nil for other provider.
- Centralize some of string literals in `constants.go`

**Related Issues/PRs (if applicable)**
Related Issue: #347 
Related PR: #424

---------

Signed-off-by: Xiaolin Lin <xlin158@bloomberg.net>
Signed-off-by: Dan Sun <dsun20@bloomberg.net>
Co-authored-by: Dan Sun <dsun20@bloomberg.net>
mathetake pushed a commit that referenced this pull request Mar 3, 2026
**Commit Message**

Add proxy URL option for Azure authentication.


**Related Issues/PRs (if applicable)**
Related PR: #445

---------

Signed-off-by: Xiaolin Lin <xlin158@bloomberg.net>
mathetake pushed a commit that referenced this pull request Mar 3, 2026
**Commit Message**

Fix APISchema to support response_format.

**Related Issues/PRs (if applicable)**

Related PR: #445

---------

Signed-off-by: Xiaolin Lin <xlin158@bloomberg.net>
mathetake pushed a commit that referenced this pull request Mar 3, 2026
**Commit Message**

Updating support for accessing azure via OIDC in addition to the already
implemented access via access secret. Token retrieved from OIDC will be
exchanged for an azure access token which will be store the same way as
getting token via client secret/id and tenant id.

Key changes
- renamed azure_token_provider -> azure_secret_token_provider (since
it's client secret specific)
- generalized new azure_token_provider to have TokenProviders provider
federated tokens
- Azure tries to create token provider from oidc if available else
client secret

**Related Issues/PRs (if applicable)**

#445 

Tested on own cluster and verified that secret access token was
generated + same credentials appeared on extproc filter config file +
able to query azure

---------

Signed-off-by: Aaron Choo <achoo30@bloomberg.net>
Co-authored-by: Dan Sun <dsun20@bloomberg.net>
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.

2 participants