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

Allow anyone on the team to generate the configuration changelog #21486

Closed
wilkinsona opened this issue May 18, 2020 · 1 comment
Closed

Allow anyone on the team to generate the configuration changelog #21486

wilkinsona opened this issue May 18, 2020 · 1 comment
Assignees
Labels
type: task A general task
Milestone

Comments

@wilkinsona
Copy link
Member

wilkinsona commented May 18, 2020

Stéphane has some code for generating the configuration properties changelog. It'd be nice if we all knew how to use it, maintain it, etc.

Edit: I think this is the code.

@wilkinsona wilkinsona added the type: task A general task label May 18, 2020
@wilkinsona wilkinsona added the for: team-attention An issue we'd like other members of the team to review label May 21, 2021
@philwebb philwebb removed the for: team-attention An issue we'd like other members of the team to review label May 26, 2021
@philwebb philwebb added this to the 2.6.x milestone May 26, 2021
snicoll added a commit to snicoll/spring-boot that referenced this issue Jun 2, 2021
This commit adds an infrastructure to inspect two configuration metadata
repositories and provide predicates to extract the properties and groups
that have been added, removed, etc.

This can be used, for instance, to generate a human readable diff when
releasing a new version of the project.

See spring-projectsgh-21486
@snicoll
Copy link
Member

snicoll commented Jun 2, 2021

I've made progress by polishing and adding the low-level infrastructure in 568930f. Based on that, we can generate an Asciidoc file that describes the diff between the previous version and the version we've just released.

With that in place, there are two tasks that are remaining to make it a bit more high-level:

  1. Add code somewhere that would download the jars for the previous version, the just released version, extract the metadata and build the two repositories. We already have that code in my scratches project.
  2. Have a method somewhere in our codebase we can trigger to generate the diff

I am a bit stuck at this point as I don't really know where to add this code. Making this part of our build could be an option but it would have to have a dependency on the spring-boot-configuration-metadata that's far from ideal (if at all possible?).

@snicoll snicoll added the for: team-meeting An issue we'd like to discuss as a team to make progress label Jun 2, 2021
@philwebb philwebb removed the for: team-meeting An issue we'd like to discuss as a team to make progress label Jun 2, 2021
@wilkinsona wilkinsona modified the milestones: 2.6.x, 2.7.x Nov 24, 2022
@wilkinsona wilkinsona self-assigned this Jun 16, 2023
@wilkinsona wilkinsona modified the milestones: 2.7.x, 3.2.x, 3.2.0-M1 Jun 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

3 participants