changes to support usage in serverless backend development #1303
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.
A corollary to recent efforts to reduce dependence on the serverless plugin: we are also trying to eliminate internal usages of
nim
in our own development processes, replacing it withdoctl
. In order for that to work,doctl
needs some enhancements to work with serverless backend clusters that are not in production (and hence not (yet) known to the portal).The changes are all in the area of credential management. Basically, they allow both setting and interrogating credentials via their low-level OpenWhisk characteristics without using the namespace APIs.
Only those commands whose
nim
equivalents are actually used in this way have been changed. The additional flags are all hidden, since this low-level credential manipulation is not something DigitalOcean customers would ordinarily do (although there is nothing insecure about it). Having these features show up in help texts would be distracting and might lead to the impression that this feature had an important mainstream use case.