Push Snapshots Though Devops Pipelines

[Pezmc]

Description

Marked draft as I'd like some UI feedback from @joepavitt (can be completed in a follow up though!).
Edit: And test failures

Key features:

• A stage can now be configured on deploy to either create a new snapshot, always copy the existing snapshot, or prompt
• Deploy snapshot names and descriptions are more intelligent and persist the original details along the pipeline stages
• User is prompted to select a snapshot on deploy if set as such

Edit Pipeline Stage

Improved Names

Select Snapshot to Deploy

Related Issue(s)

Fixes #2651, #2600

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on flowforge/helm to update ConfigMap Template
  • Issue/PR raised on flowforge/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[joepavitt]

I may request an info/help button get added next to the "Select Action" form row label. I'd like to it detail (one/two sentences) each of the options. I've managed to decipher what each of them means, but not sure it would be intuitive to all users.

[codecov]

Codecov Report

Merging #2818 (85f0f03) into main (b481f64) will decrease coverage by 0.06%.
Report is 129 commits behind head on main.
The diff coverage is 38.88%.

@@            Coverage Diff             @@
##             main    #2818      +/-   ##
==========================================
- Coverage   39.82%   39.76%   -0.06%     
==========================================
  Files         540      556      +16     
  Lines       19215    19837     +622     
  Branches     4551     4705     +154     
==========================================
+ Hits         7653     7889     +236     
- Misses      11562    11948     +386     

Flag	Coverage Δ
backend	75.52% <79.71%> (+0.62%)	⬆️
frontend	2.08% <0.69%> (-0.06%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
forge/db/models/Project.js	97.97% <100.00%> (+0.04%)	⬆️
forge/ee/db/models/PipelineStage.js	97.36% <100.00%> (+0.14%)	⬆️
forge/ee/db/views/PipelineStage.js	96.55% <ø> (ø)
...end/src/pages/application/PipelineStage/create.vue	0.00% <ø> (ø)
...ntend/src/pages/application/PipelineStage/edit.vue	0.00% <ø> (ø)
frontend/src/pages/instance/Snapshots/index.vue	0.00% <ø> (ø)
forge/services/snapshots.js	96.49% <96.77%> (-0.74%)	⬇️
frontend/src/api/pipeline.js	80.76% <20.00%> (-10.54%)	⬇️
...ations/20230919-01-add-action-to-pipeline-stage.js	0.00% <0.00%> (ø)
...ntend/src/pages/application/PipelineStage/form.vue	0.00% <0.00%> (ø)
... and 3 more

... and 86 files with indirect coverage changes

[knolleary]

Looks good on the backend side. One small update needed around logging.

Also to note we have two active PRs with migrations included - this one and #2738.

As it stands, #2738 must be merged first to ensure the migration ordering is preserved. That is the order I'm expecting these PRs to land in. If, for any reason, 2738 is delayed, we'll need to fixup the migration filenames.

[knolleary]

I think it would be helpful to have the configured action displayed on the stage:

Not going to block this PR for that... but would be great to get a quick follow-up that adds it.

[knolleary]

Slight rewording for the dialog

[Pezmc]

@knolleary

[Pezmc]

[knolleary]

@Pezmc looks good to me

[knolleary]

Merge when green

[Pezmc]

The test failure is not related to this PR and can be seen on main as far back as https://github.com/flowforge/flowforge/pull/2738/files, @hardillb and I are looking into the root cause, but there's no need to block this PR so merging away.