dont write workload identity to yaml file on deployment inspect #1565
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
don't write workload identity to yaml file on deployment inspect. this was breaking the flow of:
astro deployment inspect
on an existing deploymentthe breakage was happening because the new deployment's create payload would contain the Workload Identity from the previous deployment. instead we can leave the value empty upon
astro deployment inspect
, and the API will default it. if someone has an override to pass in, they can enter it in the deployments-as-code file.🎟 Issue(s)
Related #XXX
🧪 Functional Testing
📸 Screenshots
📋 Checklist
make test
before taking out of draftmake lint
before taking out of draft