Handle nil obj when processing custom actions #1700
Merged
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.
If an application has a missing resource, running a custom action CLI command will cause a panic on the CLI. The CLI will make a call to the ManageResource endpoint, and the server will return a nil object that the CLI will try to operate on. This PR addresses the panic by adding a nil check on the CLI. Before the fix, the CLI will produce a stacktrace like the following: