[chaule97]

Forward port of #537 from 16.0.

Right now the FastAPI documentation endpoints (Swagger, Redoc, OpenAPI) of every endpoint can be reached by anyone. Some deployments don't need them, and some aren't allowed to expose them.

This PR adds an Expose FastAPI docs checkbox (expose_doc_urls) to the FastAPI endpoint form. When it is unticked,
docs_url, redoc_url and openapi_url are set to None on the FastAPI app, so those routes return 404. Changing the field rebuilds the app.

[oca-cla-bot]

All commit authors signed the Contributor License Agreement.

[OCA-git-bot]

Hi @lmignon,
some modules you are maintaining are being modified, check this out!

[chaule97]

Hi @PicchiSeba, this is a forward port of your #537 to 17.0. The OCA CLA bot reports that picchiseba+git@gmail.com is not covered by a CLA. Could you sign it (or add this email to your existing CLA) at https://odoo-community.org/cla? Thanks!

[PicchiSeba]

@chaule97
I'm unable to sign because the page says the following

For 1 commits across 1 repositories with email address picchiseba@gmail.com.

Cannot proceed, picchiseba@gmail.com is not verified with GitHub. Please complete verification and return here to sign.

Which points me to the docs https://docs.github.com/en/account-and-profile/how-tos/email-preferences/verifying-your-email-address

But my email is verified

I think the underlying issue is the fact that my GH email is
picchiseba**+git**@gmail.com

and not picchiseba@gmail.com as it's stated in the CLA page.

I will try to contact the OCA administrators to fix this

[chaule97]

Hi @PicchiSeba, I have updated the author's email to picchiseba@gmail.com. is this okay?

[PicchiSeba]

Code Review: LGTM

[PicchiSeba]

@chaule97

Hi @PicchiSeba, I have updated the author's email to picchiseba@gmail.com. is this okay?

I have workflows setup with my email depending on the value after the "+" character and I can't easily change them rn. I wrote to the administrators to see if we can find a solution.
If it's not a problem I would ask you to wait until they answer me. But if in a week the issue is still not resolved, this weekend I'll update my email and verify the CLA with it

[PicchiSeba]

@chaule97
I applied a temporary fix by submitting the CLA with my company email.
You can re-commit provided you replace the email starting with "picchiseba" with sebastiano.picchi@pytech.it.

I don't want to keep us both waiting

[chaule97]

@chaule97 I applied a temporary fix by submitting the CLA with my company email. You can re-commit provided you replace the email starting with "picchiseba" with sebastiano.picchi@pytech.it.

I don't want to keep us both waiting

Thanks @PicchiSeba , it worked. Please review both version 18.0 and 19.0