deployment name not found returns error

[sunkickr]

Description

If the user supplies a deployment name that does not exist an error is returned similar to what happens if a user supplies a deployment ID that does not exits

🎟 Issue(s)

• astro deploy -n [name] picks a default deployment in case not found, should fail instead #1071

🧪 Functional Testing

manual testing

📸 Screenshots

📋 Checklist

• Rebased from the main (or release if patching) branch (before testing)
• Ran make test before taking out of draft
• Ran make lint before taking out of draft
• Added/updated applicable tests
• Tested against Astro-API (if necessary).
• Tested against Houston-API and Astronomer (if necessary).
• Communicated to/tagged owners of respective clients potentially impacted by these changes.
• Updated any related documentation

[codecov]

Codecov Report

Base: 87.83% // Head: 87.83% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (1725b66) compared to base (b041b32).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1074   +/-   ##
=======================================
  Coverage   87.83%   87.83%           
=======================================
  Files         113      113           
  Lines       10641    10642    +1     
=======================================
+ Hits         9346     9347    +1     
  Misses        760      760           
  Partials      535      535           

Impacted Files	Coverage Δ
cloud/deployment/deployment.go	90.90% <100.00%> (+0.02%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.