Skip to content

UI: Fix shape of response anticipated from feature-flags endpoint#10684

Merged
chelshaw merged 2 commits into
masterfrom
ui/fix-feature-flag-response-read
Jan 11, 2021
Merged

UI: Fix shape of response anticipated from feature-flags endpoint#10684
chelshaw merged 2 commits into
masterfrom
ui/fix-feature-flag-response-read

Conversation

@chelshaw
Copy link
Copy Markdown
Contributor

After testing with the real endpoint, I discovered that the shape of the data does not include a data key as initially thought. This fixes the response parsing and the test so that it works as expected with the live endpoint.

@chelshaw chelshaw merged commit 0da3cc7 into master Jan 11, 2021
@chelshaw chelshaw deleted the ui/fix-feature-flag-response-read branch January 11, 2021 20:45
chelshaw added a commit that referenced this pull request Jan 11, 2021
…0684)

* Fix shape of response anticipated from feature-flags endpoint

* Add changelog
chelshaw added a commit that referenced this pull request Jan 11, 2021
…0684) (#10685)

* Fix shape of response anticipated from feature-flags endpoint

* Add changelog
pull Bot pushed a commit to Zezo-Ai/vault that referenced this pull request Nov 7, 2025
JeremiahWork pushed a commit to JeremiahWork/vault that referenced this pull request Nov 21, 2025
* VAULT-40037 Updates to PKI observations (hashicorp#10200)

* WIP

* VAULT-40037 Updates to PKI observations

* review feedback

* public key size

* make fmt

* issuerId for sign self issued

* remove confusing issuer_name

* remove unused var

* whoops common name

* role -> role_name

* role name

* VAULT-40618 Update PKI observation timestamps to use RFC-3339 format (hashicorp#10560)

* VAULT-40672 public key information for sign intermediate (hashicorp#10684)

Co-authored-by: Violet Hynes <violet.hynes@hashicorp.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants