chore(build): ephemeral rename, nav items

[san7ket]

What's included

...

How to test

Example

...

Updates issue/story

[codecov-commenter]

Codecov Report

Merging #1051 (9ef7419) into dev (07ed88c) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1051   +/-   ##
=======================================
  Coverage   93.63%   93.63%           
=======================================
  Files         123      123           
  Lines        4274     4274           
  Branches     1743     1743           
=======================================
  Hits         4002     4002           
  Misses        254      254           
  Partials       18       18           

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 07ed88c...9ef7419. Read the comment docs.

[cdcabrera]

@san7ket few pieces

• commit message needs to be updated to reflect scope for tracking/changelog purposes, recommend something like
  • chore(build): rename, openshift container or chore(build): ephemeral rename, openshift or fix(build): ... if its an error fix. there's also a message length limit
• next, dev/feature is being planned for merge into main next week. (merging into main at this time indicates a priority over the current work lined up for RHEL VDC)
  • As much as we enjoy rebasing feature work, is this rename a make/break type scenario?
  • Can this PR be redirected to point at dev instead?

[san7ket]

@san7ket few pieces

• commit message needs to be updated to reflect scope for tracking/changelog purposes, recommend something like

  • chore(build): rename, openshift container or chore(build): ephemeral rename, openshift or fix(build): ... if its an error fix. there's also a message length limit

• next, dev/feature is being planned for merge into main next week. (merging into main at this time indicates a priority over the current work lined up for RHEL VDC)

  • As much as we enjoy rebasing feature work, is this rename a make/break type scenario?
  • Can this PR be redirected to point at dev instead?

Thanks, for the comments, I don't think it is urgent, I thought the merge job would run on main branch, but I see that's not the case. I have updated the branch to dev and will improve the commit message, also I would like to use this as a testing PR to play around with left nav in EE, if that's possible. I will also mark it as draft until I can figure out a way to make the ephemeral EE as close to stage as possible.

[cdcabrera]

@san7ket that works for us! applied the "build:hold" label... if/when this is ready to go just give us/me a heads up

[san7ket]

/retest

[san7ket]

@cdcabrera we can merge this, we now have a way to navigate to these left nav items

[san7ket]

@cdcabrera Any pointers as to why checks are failing

[cdcabrera]

@san7ket apologies we missed your note about merging. I can bring the PR up-to-date.

Do you still want this merged? And can we shut the other PR with your name on it down?

[cdcabrera]

@san7ket we brought this PR up-to-date, however...
RHEL and OpenShift are covered now in the stage-beta environment where this PR would merge first... we're assuming this can be shut down now?

about the pr failing, if curious

• Looks like the GitHub CI cache was suffering from an outdated package failure... we just removed the cache files and restarted the job
• Also, the dist output testing checks against the yaml menu file for coverage for existing product configs in the repo. That check/snapshot needs to be updated every time the yaml file is adjusted around the menu... (it also happens to be a little hidden in the process)
  1. update the NPM packages with $ yarn
  2. run $ yarn build to get the failure and available files
  3. next run $ yarn test:integration-dev follow the directions to update the file
  4. finally commit any changes with your PR

[san7ket]

Apologies for delay, both the PR's related to the PRchecks are blocked due to the new navigation (Business --> Subscriptions)change that is implemented in the stage but the changes have not yet propagated to the frontend-operator (last time I checked ) for Ephemeral environments. The issue is being tracked at https://issues.redhat.com/browse/RHCLOUD-25569. I can recheck again this week if anything has changed in EE. Meanwhile, Would it make sense to hold this and 1072 PR.

[san7ket]

/retest

[san7ket]

@cdcabrera Tested this with latest code, we can merge this, this is needed to nav inbetween pages RHEL to openshift and vice versa in ephemeral envs.

[cdcabrera]

@san7ket much appreciated on the heads up!

we'll go ahead and rebase this and get it merged today 20230815 spoke out of turn, see review

[cdcabrera]

Looks like I need to double check something on the integration check before we merge...

[cdcabrera]

Ok, updating the left nav integration snapshot should do it. Once it passes the primary tests we'll squash it down into your original commit