8000 [BUGFIX] support YAML extension in database configuration by ibakshay · Pull Request #2372 · perses/perses · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUGFIX] support YAML extension in database configuration #2372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 25, 2024

Conversation

ibakshay
Copy link
Contributor
@ibakshay ibakshay commented Oct 24, 2024

Description

This PR fixes #2371

Screenshots

Checklist

  • Pull request has a descriptive title and context useful to a reviewer.
  • Pull request title follows the [<catalog_entry>] <commit message> naming convention using one of the
    following catalog_entry values: FEATURE, ENHANCEMENT, BUGFIX, BREAKINGCHANGE, DOC,IGNORE.
  • All commits have DCO signoffs.

UI Changes

  • Changes that impact the UI include screenshots and/or screencasts of the relevant changes.
  • Code follows the UI guidelines.
  • Visual tests are stable and unlikely to be flaky.
    See Storybook
    and e2e docs for more details. Common issues
    include:
    • Is the data inconsistent? You need to mock API requests.
    • Does the time change? You need to use consistent time values or mock time utilities.
    • Does it have loading states? You need to wait for loading to complete.

Signed-off-by: Akshay Iyyadurai Balasundaram <akshay.iyyadurai.balasundaram@sap.com>
Signed-off-by: Akshay Iyyadurai Balasundaram <akshay.iyyadurai.balasundaram@sap.com>
Comment on lines +6 to +10
},
"spec": {
"display": {
"name": "perses"
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added spec.display.name since gopkg.in/yaml.v3 and encoding/json marshalers handle nil structs differently. Without this initialization, gopkg.in/yaml.v3 would omit the entire 'spec' field while encoding/json keeps it as an empty spec object.
You can see this behavior here: https://go.dev/play/p/kv0gT5GZt6M

Without a spec object the UI fails to load.
image

Copy link
Member
8000

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mmm it's weird because the UI is getting a JSON not a YAML format so spec should be initialised in the API response.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue is happening much before actually. The issue is happening during the provisioning of file database during the application start up.

So, when the config.database.file.extension is "yaml" extension, a project manifest in local_db/projects folder looks like the below snippet.

kind: Project
metadata:
    name: perses
    createdAt: 2024-10-24T18:48:14.174051Z
    updatedAt: 2024-10-24T18:48:14.174051Z
    version: 0

However, when the config.database.file.extension is "json", a project manifest in local_db/projects looks like the below snippet.

{
  "kind": "Project",
  "metadata": {
    "name": "incredibleproject",
    "createdAt": "2024-10-24T18:49:56.921669Z",
    "updatedAt": "2024-10-24T18:49:56.921669Z",
    "version": 0
  },
  "spec": {}
}

The marshalling happens in this line

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I mean is it shouldn't happen actually.

Because when the frontend is requesting the backend for anything, the response will be marshalled in JSON. So whatever the format is in the database, once it is sent to the frontend, the format is JSON.

So probably there is another thing to fix there. But it's not that urgent.

Signed-off-by: Akshay Iyyadurai Balasundaram <akshay.iyyadurai.balasundaram@sap.com>
Copy link
Member
@Nexucis Nexucis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the fix @ibakshay !

@Nexucis Nexucis merged commit 7b7af5e into perses:main Oct 25, 2024
18 checks passed
ibakshay added a commit to ibakshay/perses-operator that referenced this pull request Nov 28, 2024
Signed-off-by: Akshay Iyyadurai Balasundaram <akshay.iyyadurai.balasundaram@sap.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

YAML Database Configuration Causes JSON Marshaling Errors
2 participants
0