You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fuyao Li (Jira)" <ji...@apache.org> on 2022/05/03 23:08:00 UTC
[jira] [Updated] (FLINK-27483) Support adding custom HTTP header for HTTP based Jar fetch
[ https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fuyao Li updated FLINK-27483:
-----------------------------
Summary: Support adding custom HTTP header for HTTP based Jar fetch (was: Support adding HTTP header for HTTP based Jar fetch)
> 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 artifactory (like Oauth tokens, 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)