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

match with google cloud: allow disabling the application default credentials prompt #14500

Closed
jfaust opened this issue Mar 29, 2019 · 6 comments

Comments

@jfaust
Copy link

jfaust commented Mar 29, 2019

Feature Request

Right now, using application default credentials with GCP and match, every time I run a match operation it asks:

[11:07:58]: Do you want to use this system's Google Cloud application default keys? (y/n)

This is unnecessary, in what is otherwise a command that requires no user input.

Motivation Behind Feature

We run match in various developer scripts, and are attempting to switch from git to GCP - this effectively blocks the transition.

Feature Description

Add an option to match, something like google_cloud_prompt_for_application_credentials(false).

Alternatively, just remove the confirmation prompt entirely, as I'm not sure what benefit it provides.

Alternatives or Workarounds

yes | fastlane match ...

@fastlane-bot
Copy link

It seems like you have not included the output of fastlane env

To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

@jfaust
Copy link
Author

jfaust commented Apr 10, 2019

@mattmckeon looks like you did the work to enable application credentials - thoughts? I'm happy to get a PR going but am not sure the preferred solution.

@fastlane-bot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@jfaust
Copy link
Author

jfaust commented May 13, 2019

@fastlane-bot this is still an issue... I'm waiting on guidance for the preferred solution

@fastlane-bot
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest fastlane version and check if that solves the issue. Let us know if that works for you by adding a comment 👍

@fastlane-bot
Copy link

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@fastlane fastlane locked and limited conversation to collaborators Aug 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants