-
Notifications
You must be signed in to change notification settings - Fork 135
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
Add ip address whitelist UI to manage satellites page for itless #2836
Add ip address whitelist UI to manage satellites page for itless #2836
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2836 +/- ##
==========================================
- Coverage 63.54% 62.47% -1.07%
==========================================
Files 199 202 +3
Lines 4301 4397 +96
Branches 777 783 +6
==========================================
+ Hits 2733 2747 +14
- Misses 1559 1641 +82
Partials 9 9
|
@florkbr do we want this to be baked into chrome? Can this be its own module? |
@Hyperkid123 I don't think it necessarily needs to be baked into chrome - I just started from where the UI lived today. Do you have any suggestions or thoughts on where the new module could/should be placed? |
@florkbr a new module :) Like the widget UI. |
174a06c
to
8f7bab3
Compare
When deploying this in our itless env I'm seeing the same pod crash loop as noted in: #2922 |
ccdf9ca
to
5c92b08
Compare
@@ -38,11 +47,6 @@ const SatelliteToken: React.FC = () => { | |||
<Page | |||
className="chr-c-all-services" | |||
onPageResize={null} // required to disable PF resize observer that causes re-rendring issue | |||
header={ | |||
<Masthead className="chr-c-masthead"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Hyperkid123 since we are now exposing this as a module from chrome at /insights/satellite
- this is causing the insights masthead and nav to render around the module (hence removing the masthead here otherwise we see duplicates).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this page require some unique layout?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No - the content is just a bit odd/out of the ordinary as it is 3 utilities.
5c92b08
to
767fb92
Compare
frontend.yml
Outdated
@@ -19,6 +19,11 @@ objects: | |||
manifestLocation: "/apps/chrome/js/fed-mods.json" | |||
config: | |||
ssoUrl: ${SSO_URL} | |||
modules: | |||
- id: 'satellite-token' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Hyperkid123 I noticed this is duplicated with my changes in chrome-service-backend: RedHatInsights/chrome-service-backend#668. I know this is used for the frontend-operator - but can you explain why we need both? Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need both. Only the chrome service. This will become relevant and the source of truth once we have the new FEO features.
@@ -259,7 +258,6 @@ const ScalprumRoot = memo( | |||
} | |||
/> | |||
)} | |||
{ITLess() && <Route path="/insights/satellite" element={<SatelliteToken />} />} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed the react router route in ScalprumRoot in favor of the exposed module approach.
frontend.yml
Outdated
@@ -19,6 +19,11 @@ objects: | |||
manifestLocation: "/apps/chrome/js/fed-mods.json" | |||
config: | |||
ssoUrl: ${SSO_URL} | |||
modules: | |||
- id: 'satellite-token' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need both. Only the chrome service. This will become relevant and the source of truth once we have the new FEO features.
@@ -38,11 +47,6 @@ const SatelliteToken: React.FC = () => { | |||
<Page | |||
className="chr-c-all-services" | |||
onPageResize={null} // required to disable PF resize observer that causes re-rendring issue | |||
header={ | |||
<Masthead className="chr-c-masthead"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this page require some unique layout?
/retest |
767fb92
to
a69b2d8
Compare
@Hyperkid123 I removed the changes to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The PR build pipeline is still failing due to the |
Depends on: RedHatInsights/chrome-service-backend#668
Utilizes mbop changes here: RedHatInsights/mbop#105
Adds a simple UI to the manage satellites page to add/remove IP address(es) WRT to our itless environments.
Marking as draft until I manually try the API requests in this PR via postman on pre-prod env.EDIT: verified API requests after deploying