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

Custom Banner messages to call-out maintenance and downtime #18719

Closed
a-sudarsanan opened this issue May 23, 2023 · 0 comments · Fixed by #18827
Closed

Custom Banner messages to call-out maintenance and downtime #18719

a-sudarsanan opened this issue May 23, 2023 · 0 comments · Fixed by #18827
Assignees
Labels
kind/requirement New feature or idea on top of harbor target/2.9.0

Comments

@a-sudarsanan
Copy link

Is your feature request related to a problem? Please describe.
We have a requirement to call out downtime to the harbor server to the customers prior to the actual downtime, this could be done through a custom banner that can be closed by the users after reading or always visible on all pages.

Describe the solution you'd like
I would like to have a custom banner that can be displayed to users to inform them about planned downtime for the harbor server. The banner should have the following features:

Clear and noticeable design: The banner should be designed in a way that catches the attention of users, ensuring they notice the important information.
Customizable content: The content of the banner should be easily customizable to include specific details about the upcoming downtime, such as the date, time, and duration.
Dismissal option: Users should have the ability to close the banner after reading it, so that it doesn't obstruct their view of the website.
Persistent visibility: Alternatively, there should be an option to keep the banner visible on all pages throughout the downtime period, ensuring users are constantly reminded of the upcoming downtime.

Describe the main design/architecture of your solution
The solution can be implemented using a combination of front-end and back-end technologies. Here is a high-level overview of the design/architecture:

Front-end:
    A banner component that can be rendered on all pages of the website.
    The banner should be styled to be visually prominent, with a clear message about the planned downtime.
    The content of the banner should be easily updatable, allowing administrators to customize the information displayed.

Back-end:
    A configuration management system to store the details of the planned downtime, such as the date, time, and duration.
    An API endpoint to retrieve the downtime information from the configuration management system and provide it to the front end.
    An administration interface to allow authorized users to update the downtime details.

Describe the development plan you've considered
Here is a suggested development plan to implement the solution:

Requirement analysis: Gather detailed requirements for the banner, including design preferences, customization options, and dismissal behavior.
Front-end development:
    Implement the banner component with appropriate styling.
    Integrate the banner into the existing website template or content management system.
    Implement the dismissal functionality for the banner.
Back-end development:
    Set up a configuration management system to store the downtime details.
    Implement an API endpoint to retrieve the downtime information.
    Develop an administration interface for authorized users to update the downtime details.
Integration and testing:
    Integrate the front-end and back-end components.
    Perform thorough testing to ensure the banner functions as intended and is displayed correctly on all pages.
Deployment:
    Deploy the updated website with the downtime banner to the production environment.
    Monitor the performance and user feedback to ensure the solution meets the requirements.
Maintenance and updates:
    Regularly review and update the downtime details as needed.
    Address any user feedback or issues related to the banner.

Additional context
Add any other context or screenshots about the feature request here.

@AllForNothing AllForNothing added the kind/requirement New feature or idea on top of harbor label May 25, 2023
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 19, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 21, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 21, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 21, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jun 27, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing pushed a commit to AllForNothing/harbor that referenced this issue Jul 3, 2023
1.Fixes goharbor#18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
AllForNothing added a commit that referenced this issue Jul 3, 2023
1.Fixes #18719
2.Add Banner Message item to configuration
3.Add banner_message property to systeminfo API

Signed-off-by: AllForNothing <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/requirement New feature or idea on top of harbor target/2.9.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants