[ https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532585#comment-17532585 ]
Aitozi commented on FLINK-27483: -------------------------------- The difference is whether we need to support the authentication configuration for per job level > 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)