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

JHipster Registry docker-compose file not working on master #8190

Closed
1 task done
ruddell opened this issue Aug 30, 2018 · 2 comments
Closed
1 task done

JHipster Registry docker-compose file not working on master #8190

ruddell opened this issue Aug 30, 2018 · 2 comments
Milestone

Comments

@ruddell
Copy link
Member

ruddell commented Aug 30, 2018

Overview of the issue

Using docker-compose -f src/main/docker/jhipster-registry.yml up -d in a generated project (only on the master branch), the registry fails to launch with the following error:

Description:

Binding to target [Bindable@235a0c16 type = io.github.jhipster.config.JHipsterProperties, value = 'provided', annotations = array<Annotation>[@org.springframework.boot.context.properties.ConfigurationProperties(ignoreInvalidFields=false, ignoreUnknownFields=false, value=jhipster, prefix=jhipster)]] failed:

    Property: jhipster.security.authentication.jwt.base64-secret
    Value: bXktc2VjcmV0LXRva2VuLXRvLWNoYW5nZS1pbi1wcm9kdWN0aW9uLWFuZC10by1rZWVwLWluLWEtc2VjdXJlLXBsYWNl
    Origin: "jhipster.security.authentication.jwt.base64-secret" from property source "bootstrapProperties"
    Reason: The elements [jhipster.security.authentication.jwt.base64-secret] were left unbound.

Action:

Update your application's configuration

Motivation for or Use Case

The provided docker-compose files should work, this is also causing the Travis logs for microservices to be extremely long and hard to read

Reproduce the error

Run docker-compose -f src/main/docker/jhipster-registry.yml up -d in a generated project (from the master branch)

Related issues

Looks like it's related to the recent base64 secret key changes

Suggest a Fix

Not sure

JHipster Version(s)

Master only

JHipster configuration
.yo-rc.json file
{
  "generator-jhipster": {
    "promptValues": {
      "packageName": "com.mycompany.myapp",
      "nativeLanguage": "en"
    },
    "jhipsterVersion": "5.2.1",
    "applicationType": "microservice",
    "baseName": "ms",
    "packageName": "com.mycompany.myapp",
    "packageFolder": "com/mycompany/myapp",
    "serverPort": "8081",
    "authenticationType": "jwt",
    "cacheProvider": "hazelcast",
    "enableHibernateCache": true,
    "websocket": false,
    "databaseType": "sql",
    "devDatabaseType": "h2Disk",
    "prodDatabaseType": "mysql",
    "searchEngine": false,
    "messageBroker": false,
    "serviceDiscoveryType": "eureka",
    "buildTool": "maven",
    "enableSwaggerCodegen": false,
    "jwtSecretKey": "bXktc2VjcmV0LXRva2VuLXRvLWNoYW5nZS1pbi1wcm9kdWN0aW9uLWFuZC10by1rZWVwLWluLWEtc2VjdXJlLXBsYWNl",
    "enableTranslation": true,
    "testFrameworks": [],
    "jhiPrefix": "jhi",
    "clientPackageManager": "yarn",
    "nativeLanguage": "en",
    "languages": [
      "en"
    ],
    "skipClient": true,
    "skipUserManagement": true
  }
}
  • Checking this box is mandatory (this is just to show you read everything)
@jdubois
Copy link
Member

jdubois commented Aug 30, 2018

Yes that's because we need a new JHipster Registry release for that new version.

I'm currently doing it in #8165 (and testing at that very moment!)

@jdubois jdubois closed this as completed Aug 30, 2018
@jdubois
Copy link
Member

jdubois commented Aug 30, 2018

@ruddell that should be OK with jhipster/jhipster-registry@0f6c9a7 but I'm still testing (the image is not built yet on Docker Hub)

@jdubois jdubois added this to the 5.3.0 milestone Sep 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants