-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
R4RFC: Workload spec update for maven artifacts #741
Comments
@jwntrs can you add "Maven" to the subject to clarify this isn't related to artifact tracing |
related: https://github.com/nulldriver/maven-resource (concourse) resource_types:
- name: maven-resource
type: registry-image
source:
repository: nulldriver/maven-resource
tag: latest
resources:
- name: artifact
type: maven-resource
source:
url: https://myrepo.example.com/repository/maven-releases/
snapshot_url: https://myrepo.example.com/repository/maven-snapshots/
artifact: com.example:example-webapp:jar
username: myuser
password: mypass
repository_cert: |
-----BEGIN CERTIFICATE-----
MIIEowIBAAKCAQEAtCS10/f7W7lkQaSgD/mVeaSOvSF9ql4hf/zfMwfVGgHWjj+W
<Lots more text>
DWiJL+OFeg9kawcUL6hQ8JeXPhlImG6RTUffma9+iGQyyBMCGd1l
-----END CERTIFICATE----- |
@cirocosta do you know what the upstream plans are for specifying Maven |
Implemented using params |
Repository owner
moved this from Pre-IPM
to Closed
in Cartographer OSS
Oct 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
Currently the workload spec has fields for
source.git
andsource.image
, neither of which is suitable for basing a workload off a maven artifact. We are requesting an RFC that proposes an update to the workload spec to address this use case.Open question
What about S3 artifacts (fluxcd Bucket resource)? Would we treat these the same as maven artifacts?
The text was updated successfully, but these errors were encountered: