[
https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534627#comment-17534627
]
Fuyao Li commented on FLINK-27483:
----------------------------------
I agree with Gyula, I guess we can create a sessionJobFlinkConfiguration field
inside sessionJobSpec class.
Under this field, user could config job specific headers. This config will be
owned by sessionJobSpec, perferrably not belonging to cluster level config. As
such, this can be defined totally at session job level.
I will try to propose some code based on this idea. If Aitozi already started
the work, please let me know. Thanks.
> Support adding custom HTTP header for HTTP based Jar fetch
> ----------------------------------------------------------
>
> Key: FLINK-27483
> URL: https://issues.apache.org/jira/browse/FLINK-27483
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Fuyao Li
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> Hello Team,
> I noticed this https://issues.apache.org/jira/browse/FLINK-27161, which could
> enable users to specify a URL to fetch jars.
> In many cases, user might want to add some custom headers to fetch jars from
> remote private artifactory (like Oauth tokens, api-keys, etc).
> adding a field called artifactoryJarHeader will be very helpful.
> This field can be of array type.
> [key1, value1, key2, value2]
> It seems the current ArtifactManager doesn't support specify a custom header.
> Please correct me if I am wrong.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
