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

[API Change] use project_id from json, instead of credentials #460

Merged
merged 2 commits into from Jun 7, 2023

Conversation

k-okada
Copy link
Member

@k-okada k-okada commented Apr 25, 2023

if we have google credential file

{
  "type": "service_account",
  "project_id": "foo",
...
}

and use launch file such as

  <include file="$(find dialogflow_task_executive)/launch/dialogflow_ros.launch">
    <arg name="credential" value="$(arg google_credentials_json)" />
    <arg name="project_id" value="bar" />
</launch>

it still uses foo project.

This PR override credential setting and use project_id from rosparam.

This PR changes existing launch files that wrongly set project_id in launch file, which was ignored, will be effective.

@k-okada
Copy link
Member Author

k-okada commented Apr 25, 2023

shoud we add override_credential_project_id option?

@mqcmd196
Copy link
Member

I can hardly imagine when the situation

if we have google credential file

{
"type": "service_account",
"project_id": "foo",
...
}
and use launch file such as

it still uses foo project.

occurs. Does someone want to change project_id after the credential file from GCP has been generated?

@k-okada
Copy link
Member Author

k-okada commented Apr 28, 2023

having multiple credential files is too complex for new useres, for example jsk-ros-pkg/jsk_robot#1792 uses one file for chat, NLP and dialogflow.
BTW, Can we share credential file over different agent ?

@mqcmd196
Copy link
Member

having multiple credential files is too complex for new useres, for example jsk-ros-pkg/jsk_robot#1792 uses one file for chat, NLP and dialogflow.

I see.

BTW, Can we share credential file over different agent ?

Do you mean that we generate 2 dialogflow agents and share keys between them? I think we can't do that. When we create dialogflow agent, dialogflow creates another GCP project.

@k-okada
Copy link
Member Author

k-okada commented Jun 7, 2023

@mqcmd196 I think we can. Here, we have two agents, collaborative remembering and facial expression,
Screenshot from 2023-06-07 13-25-50

Screenshot from 2023-06-07 12-03-49

and both projects have granted permissions to eternal-byte IAM, so in this example (
https://github.com/jsk-ros-pkg/jsk_robot/pull/1792/files#diff-1b50ec7cff80b4d692c0044c454c168b226ff9011d2e7faed4a48cfcdb87b5b3R9 ) user has access to both collaborative remoembering and facial expression

Screenshot from 2023-06-07 13-18-53

Screenshot from 2023-06-07 13-17-38

@k-okada k-okada merged commit e7305c8 into jsk-ros-pkg:master Jun 7, 2023
10 checks passed
@k-okada k-okada deleted the fix_dialogflow branch June 7, 2023 04:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants