k8s-create-secret Support for non-existing secrets

Hi,

are there any considerations to support deployment of secrets for the first time, i.e. when secrets do not yet exist? I am aware that the documentation says: Create a generic secret or docker-registry secret in Kubernetes cluster, replacing the secret if it already exists.

Currently, using the action in this scenario results in:

Warning: Failed to delete secret with statusCode: 404
Warning: {}
Deleting secret:
undefined
Error: SyntaxError: Unexpected token = in JSON at position 27

IMHO it would be quite useful to support this.

Thanks

Jun 09 '23 11:06 JeannedArk

This issue is idle because it has been open for 14 days with no activity.

Jun 23 '23 12:06 github-actions[bot]

I think it is actually deleting the secret and not able to parse the result json.

Sep 28 '23 22:09 bownux

This issue is idle because it has been open for 14 days with no activity.

Oct 13 '23 00:10 github-actions[bot]

Hi, is there any update on this? I noticed this problem concerns all versions above v2 and secrets that are defined as 'generic' Assuming, initially, the specific secret doesn't exist, and providing base64 value into the data key, the action fails with the following error: Warning: Failed to delete secret with statusCode: 404 Warning: {} Deleting secret: undefined Error: SyntaxError: Unexpected token h in JSON at position 0

Mar 22 '24 09:03 PiotrDevCAN