Skip to content

[fwaas_v2]: proper ParseResponse handling#3189

Merged
EmilienM merged 1 commit intogophercloud:masterfrom
kayrus:parse-response
Oct 4, 2024
Merged

[fwaas_v2]: proper ParseResponse handling#3189
EmilienM merged 1 commit intogophercloud:masterfrom
kayrus:parse-response

Conversation

@kayrus
Copy link
Copy Markdown
Contributor

@kayrus kayrus commented Sep 26, 2024

Fixes #3184

@github-actions github-actions bot added the edit:networking This PR updates networking code label Sep 26, 2024
@kayrus kayrus requested a review from a team September 26, 2024 21:53
@github-actions github-actions bot added the semver:patch No API change label Sep 26, 2024
@kayrus kayrus changed the title [core]: proper ParseResponse handling [fwaas_v2]: proper ParseResponse handling Sep 26, 2024
@coveralls
Copy link
Copy Markdown

Coverage Status

coverage: 78.726% (+0.01%) from 78.716%
when pulling 3e74ae8 on kayrus:parse-response
into dc2e6a5 on gophercloud:master.

@EmilienM EmilienM merged commit abca462 into gophercloud:master Oct 4, 2024
@kayrus kayrus added the backport-v2 This PR will be backported to v2 label Oct 4, 2024
@kayrus kayrus deleted the parse-response branch October 4, 2024 07:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-v2 This PR will be backported to v2 edit:networking This PR updates networking code semver:patch No API change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fwaas_v2: doesn't extract HTTP headers

3 participants