Comments (19)
Original comment by [email protected]
on 19 Feb 2013 at 6:44
- Changed state: Accepted
from appengine-maven-plugin.
There are some ways to do this, I'll see about putting some docs together.
Original comment by [email protected]
on 19 Feb 2013 at 6:48
- Added labels: Type-Enhancement
- Removed labels: Type-Defect
from appengine-maven-plugin.
using --oauth2 with the first appcfg update would be much better, no?
Original comment by [email protected]
on 11 Apr 2013 at 3:57
from appengine-maven-plugin.
The main use case for this is automated deploys from ci build slaves...
where would we pass in/store the tokens?
Original comment by [email protected]
on 11 Apr 2013 at 5:57
from appengine-maven-plugin.
Hey Matt,
"There are some ways to do this"
Can you name a few ways to do this or provide some pointers? Of course I want
to use this with our CI server. Without this feature I cannot use the plugin.
Thanks,
Ingo
Original comment by [email protected]
on 17 Apr 2013 at 1:07
from appengine-maven-plugin.
One good way to store credentials would be to use Maven server password
encryption:
http://maven.apache.org/guides/mini/guide-encryption.html
That said, I'm really confused about the current behavior. I turned off OAuth2
by including
<appengine.oauth2>false</appengine.oauth2>
in my pom.xml file. However, I was completely surprised when I ran "mvn
appengine:update" and it WORKED without prompting for any email or password!
Where in the world is it getting credentials to update my app?
Original comment by [email protected]
on 21 Apr 2013 at 5:33
from appengine-maven-plugin.
OK, found it: a cookie stored in ~/.java/.userPrefs. Sorry for the digression.
Original comment by [email protected]
on 21 Apr 2013 at 6:42
from appengine-maven-plugin.
Hi,
I am having the same problem of not knowing how to use the plugin on my CI
server.
I don't have access to the CI server to plant an oauth token on the users
folder.
Matt, did you find the time yet to write those docs? ;)
Thanks
Original comment by [email protected]
on 12 Jun 2013 at 12:20
from appengine-maven-plugin.
Maven has a <server> declaration that is perfect for this. One can define their
credentials in settings.xml and the plugin just needs to know the id of the
server to pull the username and password.
Original comment by [email protected]
on 3 Oct 2013 at 10:19
from appengine-maven-plugin.
How do you specify which <server> to pick form the settings.xml?
Original comment by [email protected]
on 17 Oct 2013 at 7:48
from appengine-maven-plugin.
In the old maven-gae-plugin, there was a server configuration parameter that
specified this, defaulting to "appengine.google.com"
Original comment by [email protected]
on 17 Oct 2013 at 8:10
from appengine-maven-plugin.
I managed to work around this issue using this config:
<plugin>
<groupId>com.google.appengine</groupId>
<artifactId>appengine-maven-plugin</artifactId>
<version>1.8.6</version>
<configuration>
<email>[email protected]</email>
<oauth2>false</oauth2>
<noCookies>true</noCookies>
<passin>true</passin>
</configuration>
</plugin>
and by invoking the update goal like this:
mvn clean appengine:update <<< "yourPassW00rd"
Original comment by [email protected]
on 18 Oct 2013 at 5:42
from appengine-maven-plugin.
The problem is that your password is in clear in the command line in your CI
server. Not really nice in terms of security.
Original comment by [email protected]
on 22 May 2014 at 3:57
from appengine-maven-plugin.
Yes I totally agree with you. Picking the credentials from the <server> in
Maven's settings.xml would be a much cleaner solution.
Original comment by [email protected]
on 22 May 2014 at 4:03
from appengine-maven-plugin.
i tried to use this command: mvn clean appengine:update <<< "yourPassW00rd"...
but how do i do it? The Travis-ci console keeps saying my email and password do
not match.
I though it was just substituting yourPassW00rd with my google app engine
password.
Original comment by [email protected]
on 28 May 2014 at 11:01
from appengine-maven-plugin.
@simon - this does not work in Jenkins. Not the standard way at least.
We need this...
Original comment by [email protected]
on 8 Oct 2014 at 6:43
from appengine-maven-plugin.
I forked the project and merged in the settings.xml authentication from the old
kindleit plugin.
https://github.com/rdwallis/appengine-maven-plugin
Needs some codestyle attention but otherwise works well.
No idea how to issue a PR to this project though. Are there contribution
guidelines anywhere?
Original comment by [email protected]
on 22 Nov 2014 at 4:28
from appengine-maven-plugin.
'+'1000! You rock!
Original comment by [email protected]
on 22 Nov 2014 at 4:29
from appengine-maven-plugin.
It's an old ticket, but since it is still open: ClientLogin
has been deprecated and removed in April, so Simon's approach does not work anymore. Related configuration options (email
, oauth2
, noCookies
, passin
in appengine-maven-plugin
and corresponding command line arguments in appcfg.sh
) are still around but seem useless. So storing email and password in settings.xml
does not look feasible anymore.
It would be good however to document the recommended approach for headless CI servers, e.g. how to setup them to use OAuth2 with a service account.
from appengine-maven-plugin.
Related Issues (20)
- Better integration with CircleCI
- Unable to deploy with `--use_google_application_default_credentials` option from Debian Jessie GCE instance. HOT 5
- Doesn't work with appengine 1.9.37 HOT 2
- specifying a custom dockerfile in configuration.dockerfile doesn't work for flex deployment
- provide mojo that starts, stops, clean without executing full lifecycle
- All unit tests fail w/ appengine-api-1.0-sdk-1.9.49.jar HOT 11
- update not working with 1.9.49 HOT 4
- Goal 'endpoints_get_discovery_doc' fails to execute on 1.9.49 HOT 3
- GAE deployment: appengine-maven-plugin:1.9.50:endpoints_get_discovery_doc : Null key for a Map not allowed in JSON
- Spring Boot Deploy HOT 1
- Google App Engine (GAE) - Flexible Environment - Jetty Issue HOT 2
- GCLOUD: ERROR: (gcloud.app.deploy) The requested resource already exists. HOT 1
- -Drun.profiles ignored during mvn appengine:deploy
- Getting 403 error but version is getting deployed with 0% traffic HOT 1
- appengine-maven-plugin vs app-maven-plugin HOT 2
- Allow running tasks without forking lifecycle.
- Unable to update app: Failed to generate quickstart-web.xml. HOT 1
- <version> seems to be required in appengine-web.xml to run locally
- Allow setting a specific port for secondary modules/services
- Project configuration is mandatory
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from appengine-maven-plugin.