fix: mark secret outputs sensitive for classic vpn Ref: #158

[qbaze]

[google-cla[bot]]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[imrannayer]

@qbaze have you tried setting these outputs sensitive in your root module code?

[github-actions[bot]]

This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[qbaze]

@imrannayer sorry for a late response

when used as a submodule it works fine but isn't it to work also as a standalone one?

are there any cons marking these sensitive in its own outputs?

[imrannayer]

@qbaze these are published as modules. Expectation is they will be used as module.

[imrannayer]

/gcbrun

[bharathkkb]

/gcbrun