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

Implements missed settings from Sunstone configuration file on FireEdge #5804

Closed
11 of 12 tasks
sbbarragan opened this issue Apr 13, 2022 · 0 comments
Closed
11 of 12 tasks

Comments

@sbbarragan
Copy link

sbbarragan commented Apr 13, 2022

Description
In the new React Sunstone missed some settings from configuration files.
This supposes to evaluate the new correct file: fireedge-server.conf or sunstone-server.conf

Progress Status

  • Branch created
  • Code committed to development branch
  • Testing - QA
  • Documentation
  • Release notes - resolved issues, compatibility, known issues
  • Code committed to upstream release/hotfix branches
  • Documentation committed to upstream release/hotfix branches
@tinova tinova added this to the Release 6.4 milestone Apr 13, 2022
rsmontero pushed a commit that referenced this issue May 10, 2022
rsmontero pushed a commit that referenced this issue May 10, 2022
(cherry picked from commit 1f78385)
rsmontero pushed a commit that referenced this issue May 10, 2022
rsmontero pushed a commit that referenced this issue May 10, 2022
(cherry picked from commit 0d50a59)
rsmontero pushed a commit that referenced this issue May 10, 2022
rsmontero pushed a commit that referenced this issue May 10, 2022
@tinova tinova modified the milestones: Release 6.4, Release 6.4.1 May 10, 2022
@tinova tinova closed this as completed May 20, 2022
rsmontero pushed a commit that referenced this issue Jul 27, 2022
(cherry picked from commit 0d50a59)
rsmontero pushed a commit that referenced this issue Jul 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants