[
https://issues.apache.org/jira/browse/FLINK-27483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17531518#comment-17531518
]
Fuyao Li edited comment on FLINK-27483 at 5/4/22 7:01 AM:
----------------------------------------------------------
Hi Aitozi, thanks for the quick reply :)
I think the reconcile interval is specified at the cluster spec level, right?
That's 60 seconds by default if I remember correctly.
I am fine with the configuration approach, I think it is like a wrapper.
Basically, the code still need to define artifactoryJarHeader under this level.
Things under this wrapper are dedicated to session jobs. Is this what you are
intending to do?
The downside of this approach is an additional intermediate layer. This seems
to be making things a little bit complicated. I guess it is very likely we
don't have much undefined fields, maybe an addition layer is overengineering?
was (Author: fuyao li):
Hi Aitozi, thanks for the quick reply :)
I think the reconcile interval is specified at the cluster spec level, right?
That's 60 seconds by default if I remember correctly.
I am fine with the configuration approach, I think it is like a wrapper.
Basically, the code still need to define artifactoryJarHeader under this level.
Things under this wrapper are dedicated to session jobs. Is this what you are
intending to do?
The downside of this approach is an additional intermediate layer seems to be
making things a little bit complicated.
> 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)
