Artifact as Manifest Source
this fiscal quarter
C
Chartreuse Meerkat
Currently, the manifest source options available in Harness are all git repositories (or a Harness file).
For our use-case, teams will be packaging their CF manifest files alongside their service assets inside each artifact.
Rather than "pre-processing" an artifact, as was supported in Harness first-gen in order to de-couple multiple artifacts packaged together, we are looking to package artifacts individually but with the manifest.yml file packaged alongside the other artifact assets.
Log In
N
Nectar Mole
Please see https://support.harness.io/hc/en-us/requests/56221 for unresolved issue identified during validation, still pending support and resolution from Harness
Shylaja Sundararajan
marked this post as
this fiscal quarter
Shylaja Sundararajan
marked this post as
next fiscal quarter
S
Safflower Unicorn
marked this post as
under review
C
Chartreuse Meerkat
This was submitted initially in Asana. A work around was provided. The work around was a temporary solution.