Provide CI values to speficy a manifest project to update

Release notes

Problem to solve

As a Developer, I want to have a simple way to update my manifest projects, so that I can deploy easily.

Intended users

User experience goal

This would be similar to how pages operates.

Example:

manifest_update:
  project:
    - 
      project: my-group/manifest-project
      path: dev
  artifacts:
    - <path spec>

Proposal

The manifest project can be configured to either commit directly to master or open an MR automatically as the result of the CI run.

The manifest project should be able to update itself in a similar manner, so a different trigger might start creating a pipeline run that creates the manifests as an artifact, and would save them to the manifest project.

Further details

Permissions and Security

  • The user running the CI job should have write access to the manifest project's master branch.

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references