Add stack to deployment response resource

[safoinme]

Describe changes

I implemented/fixed _ to achieve _.

Pre-requisites

Please ensure you have done the following:

• I have read the CONTRIBUTING.md document.
• I have added tests to cover my changes.
• I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
• IMPORTANT: I made sure that my changes are reflected properly in the following resources:
  • ZenML Docs
  • Dashboard: Needs to be communicated to the frontend team.
  • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
  • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (add details above)

[schustmi]

Do we need this for the frontend? Otherwise, in code it would also be quite easy to just fetch it from the snapshot that is already passed as part of the resources.

[safoinme]

Yes, this is mainly for front-end

[safoinme]

@schustmi does it make sense to do include_metadata=True for the stack so we get full components so it shows up in front-end? or is there an alternative to fetch that in front via ID of stack?

[schustmi]

@schustmi does it make sense to do include_metadata=True for the stack so we get full components so it shows up in front-end? or is there an alternative to fetch that in front via ID of stack?

@safoinme No I don't think that makes sense. Anything in resources is useful to show in a list of items (e.g. show the stack as a column in the deployment list), but if the frontend needs more information (like the components) on a detail page, it can easily send another request to fetch that.