-
Notifications
You must be signed in to change notification settings - Fork 273
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
connnectors: feature warnings on incompatible plugins #6525
base: next
Are you sure you want to change the base?
Changes from all commits
a9ff400
6907286
1df4887
940bbce
b49f6e4
ac8c598
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
# A valid router configuration with every incompatible | ||
# router feature turned on for testing warnings. | ||
|
||
apq: | ||
subgraph: | ||
all: | ||
enabled: true | ||
authentication: | ||
subgraph: | ||
all: | ||
aws_sig_v4: | ||
default_chain: | ||
profile_name: "my-test-profile" | ||
region: "us-east-1" | ||
service_name: "lambda" | ||
assume_role: | ||
role_arn: "test-arn" | ||
session_name: "test-session" | ||
external_id: "test-id" | ||
Comment on lines
+8
to
+19
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We actually do have full support for this with connectors. It just needs to be configured at the connector source level: authentication:
connector:
sources:
aws.lambda:
aws_sig_v4:
default_chain:
profile_name: "default"
region: "us-east-1"
service_name: "lambda"
assume_role:
role_arn: "arn:aws:iam::XXXXXXXXXXXX:role/helloexecute"
session_name: "graphql" Maybe if they have authentication settings on The ideal solution would be to detect if any connector base URL points to AWS, and warn if they haven't configured the corresponding source with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does |
||
batching: | ||
enabled: true | ||
mode: batch_http_link | ||
subgraph: | ||
all: | ||
enabled: false | ||
subgraphs: | ||
connectors: | ||
enabled: true | ||
coprocessor: | ||
url: http://127.0.0.1:8081 | ||
subgraph: | ||
all: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The |
||
request: | ||
headers: true | ||
demand_control: | ||
enabled: true | ||
mode: measure | ||
strategy: | ||
static_estimated: | ||
list_size: 10 | ||
max: 1000 | ||
headers: | ||
all: | ||
request: | ||
- propagate: | ||
matching: ^upstream-header-.* | ||
- remove: | ||
named: "x-legacy-account-id" | ||
preview_entity_cache: | ||
enabled: true | ||
subgraph: | ||
all: | ||
enabled: true | ||
rhai: | ||
scripts: "/rhai/scripts/directory" | ||
telemetry: | ||
apollo: | ||
errors: | ||
subgraph: | ||
all: | ||
send: true | ||
redact: false | ||
tls: | ||
subgraph: | ||
all: | ||
certificate_authorities: "${file./nonsense/path.crt}" | ||
traffic_shaping: | ||
subgraphs: | ||
connectors: | ||
deduplicate_query: false | ||
compression: gzip |
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.
It seems too broad to warn if the customer is using Rhai at all. It's not really incompatible - the only issue is that there is no way for them to hook into the connectors requests, which isn't something we need to warn about since they can't do it. They might mistakenly think that the subgraph lifecycle hook will be executed for a subgraph containing connectors, when it won't. But the other lifecycle hooks are still executed, and in fact we suggest that they use these for auth. I think warning here would be more confusing than anything.
My bar for a warning is that there should be a way for the customer to resolve the issue, or at least suppress it. Here, there isn't - if they need to use Rhai for auth or any other reason, they'd see this warning always.