[ConnectorsV2] Allow specifying custom global headers for a single file connector type. #245132
+240
−100
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates single file connector auth spec to allow specifying custom headers that will be added to the configured axios instance for the connector type.
For our existing connectors, we typically save any header values in the connector saved object as part of the
config. For the single file connectors, I thought it would be more dynamic to add it to theActionTypeand read it at execution time. This means that if a connector spec is updated with a new header value, existing connectors of that type (stored as saved objects) would use the updated headers the next time they're executed.