NVIDIA NeMo Secret tasks
- Use
nemo_apiwith resourcesecrets, passingworkspace="<active request workspace>"on every call. - Use
create,retrieve,list,update, anddeleteactions as needed, passing only secret references (<workspace>/<name>), names, and metadata in JSONparams, never resolved secret values. Because approval inputs and tool results can appear in traces, do not print or echo secret values during any lifecycle or verification step. - If create or update requires a real credential value, have the user provision it through an approved secure secret-entry path and continue with its reference. Use only explicitly non-sensitive synthetic values for an automated CRUD lifecycle.
- Always finish the whole lifecycle: create temporary secret, verify/list/update/delete it, then create the final verification secret.