Skip to content
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

Environment Flag Webhooks show the current date rather than the created date #2554

Closed
1 of 4 tasks
dabeeeenster opened this issue Aug 1, 2023 · 1 comment · Fixed by #2555
Closed
1 of 4 tasks
Assignees
Labels
bug Something isn't working

Comments

@dabeeeenster
Copy link
Contributor

Describe the bug

Environment Flag Webhooks show the current date rather than the created date

To Reproduce

Go to an environment with an existing webhook (Environment > Settings > Webhooks)

Expected behavior

Created date should show created date. Currently shows todays date

Screenshots

image

How are you running Flagsmith?

  • Self Hosted with Docker
  • Self Hosted with Kubernetes
  • SaaS at flagsmith.com
  • Some other way

Additional context

Add any other context about the problem here.

@dabeeeenster dabeeeenster added the bug Something isn't working label Aug 1, 2023
@dabeeeenster dabeeeenster self-assigned this Aug 1, 2023
@dabeeeenster
Copy link
Contributor Author

dabeeeenster commented Aug 1, 2023

Looks like a Frontend error. Getting this:

https://api.flagsmith.com/api/v1/environments/XXX/webhooks/

[
    {
        "id": 342,
        "url": "https://fa07-77-101-228-115.eu.ngrok.io",
        "enabled": true,
        "created_at": "2022-11-02T11:38:44.502187Z",
        "updated_at": "2022-11-02T11:38:44.502201Z",
        "secret": ""
    }
]

Which was when I created the hook. But the UI is showing https://user-images.githubusercontent.com/173290/257459337-edae9e17-9a27-4cda-9ad2-d5830cb72b6b.png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant