Una madre soltera sin un duro envió por error un mensaje a un multimillonario pidiendo dinero para leche de bebé — y entonces, todo empezó.

Una madre soltera sin un duro envió por error un mensaje a un multimillonario pidiéndole dinero para leche de bebé y ahí empezó todo.

Lucía Méndez estaba sentada en la cocina mal iluminada de su piso destartalado, con el agotamiento pesándole como una losa. Eran las dos de la madrugada y, en la habitación de al lado, su bebé, Mateo, no paraba de llorar. Llevaba horas intentando calmarlo, pero los lloros de hambre eran inconfundibles. Solo le quedaba leche en polvo para un último biberón ¿y después qué?

Como madre soltera que apenas llegaba a fin de mes, Lucía no veía salida. Su trabajo en un bar de mala muerte apenas le daba para pagar el alquiler, y menos aún para lo esencial de Mateo. Ya había empeñado su alianza para comprar comida y no podía pedir ayuda a su familiaellos tampoco tenían un euro.

(“Ofertas de vacaciones familiares”una frase publicitaria que se coló entre sus pensamientos.)

Agarró el móvil y abrió su aplicación delTitle: Add OpenAPI spec for Azure PowerShell
username_0: This is the initial OpenAPI spec for the Azure PowerShell module. We will be adding more here as we continue to develop the module.

This PR adds the following:
– OpenAPI spec for Azure PowerShell
– README.md for the spec
– PowerShell script to generate the spec from a CSV file (we plan to generate the CSV file from the module itself in the future)

### PR information
– [x] The title of the PR is clear and informative.
– [x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md).
– [x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
– [x] If applicable, the PR references the bug/issue that it fixes.
– [x] Swagger files are correctly named (e.g. the `api-version` in the path should match the `api-version` in the spec).

### Quality of Swagger
– [x] I have read the [contribution guidelines](https://github.com/Azure/azure-rest-api-specs/blob/master/.github/CONTRIBUTING.md).
– [x] My spec meets the review criteria:
– [x] The spec conforms to the [Swagger 2.0 specification](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md).
– [x] The spec follows the guidelines described in the [Swagger checklist](https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/swagger-checklist.md) document.
– [x] [Validation tools](https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/swagger-checklist.md#validation-tools-for-swagger-checklist) were run on swagger spec(s) and have all been fixed in this PR.
username_1: Can one of the admins verify this patch?
username_0: @username_3 @username_2 here is the PR for the OpenAPI spec for Azure PowerShell. Please let me know if you need anything else from me or if you have any questions.
username_0: @username_3 @username_2 have you had a chance to take a look at this? Let me know if you need any more details.
username_2: @username_3 – can you take a look at this PR and provide feedback?
username_3: @username_0, I briefly looked through the PR and had a few questions.
– For the endpoints listed in the CSV file, are these endpoints from ARM? If not, what are they?
– Is there a reason for generating the OpenAPI spec from a CSV file rather than using the existing ARM specs?
– Do you expect this spec to be updated frequently as new endpoints are added to Azure PowerShell?
username_0: @username_3 here are answers to your questions:
– No, these are not ARM endpoints. These are the endpoints that the Azure PowerShell module uses to interact with Azure. We are adding them to this spec so that we can track them and ensure that they are properly documented.
– We are generating the OpenAPI spec from a CSV file because we want to be able to track the endpoints that the Azure PowerShell module uses. We are not using the existing ARM specs because we want to be able to track the endpoints that the Azure PowerShell module uses, not the endpoints that ARM uses. In the future, we plan to automatically generate the CSV file from the module itself.
– Yes, we expect this spec to be updated frequently as new endpoints are added to Azure PowerShell. We will be adding more endpoints to this spec as we continue to develop the module.