Run promises in order

[hardillb]

Description

possible for creating/deleting k8s artefacts to fail if done out of order or too quickly.

Related Issue(s)

#114

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

[hardillb]

@elenaviter This is still work in progress, but if you get a moment can you cast an eye of these changes. (open question is how long to wait when polling)

[elenaviter]

Hello @hardillb,
I've opened followup PR on this same branch.
The code was staged on our systems and shown the problems it address are solved:

• suspend/start project is not guaranteed to succeed
• projects auth token deteriorates after FF upgrade

We are aiming to integrate it at the earliest convenience.
Thank you in advance for considering our request! We are looking forward to your valuable feedback.

[hardillb]

I've tested this locally on my K8s rig and it looks good so far.

[hardillb]

@ppawlowski when you get moment can you review this so I can deploy it to staging for more testing. Thanks

[knolleary]

Spotted some intervals that wouldn't be stopped in case of an error.