Support for non-existing secrets

[JeannedArk]

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

[github-actions]

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

[bownux]

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

[github-actions]

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

[PiotrDevCAN]

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