Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameter gkeCredentials should be optional, but isn't #66

Closed
thallgren opened this issue Dec 5, 2023 · 1 comment · Fixed by #85
Closed

Parameter gkeCredentials should be optional, but isn't #66

thallgren opened this issue Dec 5, 2023 · 1 comment · Fixed by #85
Assignees

Comments

@thallgren
Copy link

The input parameter gkeCredentials is claimed to be optional. However, failing to provide this parameter yields the following error:

Error: gkeCredentials are missing. Make sure that input parameter gkeCredentials was provided
    at new Client (/home/runner/work/_actions/datawire/infra-actions/v0.2.0/provision-cluster/lib/gke.js:35:15)
    at Object.<anonymous> (/home/runner/work/_actions/datawire/infra-actions/v0.2.0/provision-cluster/lib/registry.js:10:10)

The reason for this is that the when the const distributions declared in registry.js is initialized, it calls on the gke.Client constructor, which in turn produces the error.

@thallgren
Copy link
Author

The workaround I used to circumvent the problem was to provide a dummy credential that names a service. That works, because it is never used:

    gkeCredentials: '{"project_id": "foo"}'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants