Created by: sebastien-rosset
To initialize the configuration, developers can write the following code:
configuration = Configuration(
host = "http://example.com",
configuration.signing_info = openapi.HttpSigningConfiguration(
signing_scheme = intersight.signing.SCHEME_RSA_SHA256,
...
)
)
Or, for whatever reason, they can first create the config object, then assign the signing info:
configuration = Configuration(
host = "http://example.com"
)
...
configuration.signing_info = openapi.HttpSigningConfiguration(
signing_scheme = intersight.signing.SCHEME_RSA_SHA256,
...
)
In the first case, the host parameter is automatically passed from the Configuration object to the HttpSigningConfiguration. In the second case, the HttpSigningConfiguration.host was None. This PR fixes the problem for the second case, i.e. the developer should not have to set the parameter twice.
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/
(or Windows batch scripts under.\bin\windows
) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh
,./bin/openapi3/{LANG}-petstore.sh
if updating the code or mustache templates for a language ({LANG}
) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master
,4.3.x
,5.0.x
. Default:master
. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.