Skip to content
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.

Have the possibility to specify the spring profiles being used #1364

Open
a3aanwisse opened this issue Aug 27, 2018 · 3 comments
Open

Have the possibility to specify the spring profiles being used #1364

a3aanwisse opened this issue Aug 27, 2018 · 3 comments
Labels
status/never-stale Pin this issue to get never marked as stale by stale-bot

Comments

@a3aanwisse
Copy link

a3aanwisse commented Aug 27, 2018

Description

When using the spring-boot generator like this:

<generator>
  <includes>
    <include>spring-boot</include>
  </includes>
  <config>
    <spring-boot>
      <registry>${docker.registry.host}</registry>
      <name>${kubernetes.deploy.project}/%a:%l</name>
    </spring-boot>
  </config>
</generator>

the generated result always starts up using the default application.yml.
Is it possible to extend the plugin with an option to specify which spring profile is active so we can use this to roll out to different environments (dev, prod, acc)?

Info

We now use our own image which specifies the profile using

<entryPoint>
  <exec>
    <arg>java</arg>
    <arg>-jar</arg>
    <arg>-Dspring.profiles.active=prod</arg>
    <arg>/opt/${project.artifactId}-${project.version}.jar</arg>
  </exec>
</entryPoint>
  • f-m-p version : 3.5.41
@rhuss
Copy link
Contributor

rhuss commented Sep 4, 2018

There is already a PR #955 pending, we need to revisit it though as it unfortunately got stale over time.

But yes, we have hopefully support for spring profiles soon.

@stale
Copy link

stale bot commented Dec 3, 2018

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue/PR considered to be stale label Dec 3, 2018
@stale stale bot closed this as completed Dec 10, 2018
@rhuss rhuss reopened this Dec 11, 2018
@stale stale bot removed the status/stale Issue/PR considered to be stale label Dec 11, 2018
@stale
Copy link

stale bot commented Mar 11, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale Issue/PR considered to be stale label Mar 11, 2019
@stale stale bot closed this as completed Mar 18, 2019
@rohanKanojia rohanKanojia reopened this Mar 18, 2019
@rohanKanojia rohanKanojia added the status/never-stale Pin this issue to get never marked as stale by stale-bot label Mar 18, 2019
@stale stale bot removed the status/stale Issue/PR considered to be stale label Mar 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status/never-stale Pin this issue to get never marked as stale by stale-bot
Projects
None yet
Development

No branches or pull requests

3 participants