[
https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531506#comment-17531506
]
Aitozi edited comment on FLINK-27483 at 5/4/22 6:29 AM:
--------------------------------------------------------
I think supporting the custom headers is useful, but I'm not tend add a
dedicated field {{artifactoryJarHeader}} for it, because it only works when
jarURI is based on http, besides it's not much extendable.
I'd like to add a {{configuration}} filed in {{FlinkSessionJobSpec}} . The
field will used to control the reconcile logic like the reconcile interval,
delay and also can pass the headers for the http url. WDYT [~wangyang0918]
[~Fuyao Li] ?
was (Author: aitozi):
I think the custom headers is reasonable, but I'm not tend add a dedicated
field {{artifactoryJarHeader}} for it, because it only works when jarURI is
based on http, besides it's not much extendable.
I'd like to add a {{configuration}} filed in {{FlinkSessionJobSpec}} . The
field will used to control the reconcile logic like the reconcile interval,
delay and also can pass the headers for the http url. WDYT [~wangyang0918]
[~Fuyao Li] ?
> 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: Improvement
> Components: Kubernetes Operator
> Reporter: Fuyao Li
> Priority: Major
>
> 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)