initial support for Heroku deployment

[atomfrede]

This PR adds initial support for Heroku deployment of micronaut apps. It requires #84 and depends on upcoming changes in the main generator (thats why it is in draft mode).

• Update procfile (disable deduction, use correct order)
• Use environments constants
• update to main generator 6.10.1
• Make endsession endpoint provider agnostic (works with keycloak and okta)
• Adapt heroku and okta script for micronaut

closes #82

waiting on jhipster/generator-jhipster#11919

[mraible]

@atomfrede I'd love to have this working for a blog post I hope to write when Micronaut 2.0 is released next week (and this blueprint shortly after). Do you have permission to add more labels so I can assign it a bug bounty?

[atomfrede]

Let me check. We need to have a new main generator release for this and I would like to have jhipster/generator-jhipster#11712 merged so heroku has much more features.

[atomfrede]

@mraible I can edit the labels. I will create our defined bounty labels here too.

[JasonTypesCodes]

@atomfrede Is there anything I can do to help out with this PR?

[atomfrede]

This basically waiting for the main generator release. Everything is working.

[mraible]

@pascalgrimaud Any chance of getting a new JHipster release so we can have Heroku + Okta in the main generator?

[pascalgrimaud]

@mraible : just sent an email to our dev mailing list :)

[atomfrede]

Following is tested and working:

• mvn + jwt + git deploy ✔️
• gradle + jwt + git deploy 🔴 (Client app not served, / gives 404, locally just working fine)
• mvn + jwt + jar deploy ✔️
• gradlew + jwt + jar deploy 🔴 (Client app not served, / gives 404, locally just working fine)
• mvn + oauth + git deploy ✔️
• mvn + oauth + jar deploy ✔️
• gradle + oauth + git deploy 🔴
• gradle + oauth + jar deploy 🔴

This is the route error in the logs when using gradle

2020-06-28T20:00:35.043483+00:00 heroku[router]: at=info method=GET path="/" host=mhipster-610-gradlejwtjar.herokuapp.com request_id=a01fdf18-fb48-439a-a3b7-a6ae0d4dc570 fwd="91.39.141.105" dyno=web.1 connect=1ms service=1213ms status=404 bytes=211 protocol=https

Using maven the same router logs give a 200.

Creating the logout redirect urls is done completely on the server now (making the endsession endpoint provider agnostic see #45. So we may rename it). Will do some final manual tests tomorrow. Regarding the gradle problem I still have no idea why the frontend is not delivered, but thats not preventing this to be merged.

[atomfrede]

Good news. I have modified application working fine with okta both with login/logout and user sync. Will try to push the generator code tonight and test it again.

[JasonTypesCodes]

This is great @atomfrede. There is a lot of good stuff here.

[atomfrede]

Regarding the gradle 404s on heroku I still have no clue. The jar works just fine locally. I will have a chat with the new heroku java language owner next week maybe he has an idea or hint how to further debug it.

[atomfrede]

Somehow the builds are flaky on ci, but eventually all green here too. So from my side we could merge this after review (let's ignore the gradle app reachable on heroku for now).

[JasonTypesCodes]

I don't have experience with Heroku @atomfrede. If you feel good about this, I think it is alright. I was going to see if we could add CI for this, but it looks like you need an active Heroku account for it

[JasonTypesCodes]

Somehow the builds are flaky on ci, but eventually all green here too. So from my side we could merge this after review (let's ignore the gradle app reachable on heroku for now).

If this is a known bug we should create an issue for it right away once we merge.