Add support for hot deployment of OpenAPI files in development mode

[omatheusmesmo]

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

• You have read the contributors guide
• Your code is properly formatted according to our code style
• Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
• Pull Request contains link to the issue
• Pull Request contains link to any dependent or related Pull Request
• Pull Request contains description of the issue
• Pull Request does not include fixes for issues other than the main ticket

Fixes #1071

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

[mcruzdev]

Hi @omatheusmesmo thank you for this great contribution. Could you add test for this code?

[omatheusmesmo]

Hi @omatheusmesmo thank you for this great contribution. Could you add test for this code?

Hi @mcruzdev !

It's done. =D

[mcruzdev]

Thanks a lot @omatheusmesmo, I tested here and it is great!

[mcruzdev]

Sorry @omatheusmesmo I have tested an scenario:

• When the user adds the followingquarkus.openapi-generator.moqu.resource-dir=openapi property (not in resources dir) the hot reload does not work.

The Quarkus Roq extension does something similar (watching directory from project root dir).

[omatheusmesmo]

Sorry @omatheusmesmo I have tested an scenario:

• When the user adds the followingquarkus.openapi-generator.moqu.resource-dir=openapi property (not in resources dir) the hot reload does not work.

The Quarkus Roq extension does something similar (watching directory from project root dir).

There's no need to apologize. I'm working on fixing this—thanks for the reference!

[mcruzdev]

@omatheusmesmo for now I think we can guarantee that when I change just the file content the live reload will work as expected. We can solve the live reload dir changes in another pull request, what do you think?

[omatheusmesmo]

@omatheusmesmo for now I think we can guarantee that when I change just the file content the live reload will work as expected. We can solve the live reload dir changes in another pull request, what do you think?

Sounds good to me, I can also open a new issue about this bug.

[mcruzdev]

Thanks a lot for this pull request @omatheusmesmo!
c

ould you set for review and squash all commits? So we can merge this!

[mcruzdev]

Sorry, IDNK why this was closed

[omatheusmesmo]

Thanks a lot for this pull request @omatheusmesmo! c

ould you set for review and squash all commits? So we can merge this!

Done! 😄

[mcruzdev]

Great!

[mcruzdev]

@ricardozanini @hbelmiro we need to add backporting tag, am i right?

EDIT: We already have.

[mcruzdev]

@all-contributors please add @omatheusmesmo for code

[allcontributors]

@mcruzdev

I've put up a pull request to add @omatheusmesmo! 🎉