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

[nodejs-docs-samples/functions/scheduleinstance/index.js] How to configure projectId to control other project's vm? #1605

Closed
team-jinhong-kim opened this issue Feb 17, 2020 · 2 comments
Assignees
Labels
type: question Request for information or clarification. Not an issue.

Comments

@team-jinhong-kim
Copy link

team-jinhong-kim commented Feb 17, 2020

I changed the computer.projectId to a different value, but the following code blocks cannot run the VM in the another project.(Service Account has proper permission to handle another project's VM)

Is there are any further configuration are required? could you let me know how to change projectID field to control VMs in other projects?

const Compute = require('@google-cloud/compute');
const compute = new Compute({
  projectId: 'TARGET_PROJECT_ID'
});
       const [operation] = await compute
       .zone(payload.zone)
       .vm(instance.name)
       .start();

@yoshi-automation yoshi-automation added triage me I really want to be triaged. 🚨 This issue needs some love. labels Feb 18, 2020
@fhinkel
Copy link
Contributor

fhinkel commented Feb 25, 2020

👋 @team-jinhong-kim Thanks for opening the issue. @djmailhot could you have a look please. Thanks.

@fhinkel fhinkel added type: question Request for information or clarification. Not an issue. and removed 🚨 This issue needs some love. triage me I really want to be triaged. labels Feb 25, 2020
@fhinkel
Copy link
Contributor

fhinkel commented Mar 24, 2020

Closing this issue due to inactivity. Please re-open if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question Request for information or clarification. Not an issue.
Projects
None yet
Development

No branches or pull requests

4 participants