Use the "@redhat-cloud-services/eslint-config-redhat-cloud-services"
eslint config. This allows our styling to be standardized with other
Red Hat Insights apps. Also, remove now unneeded eslint packages.
/tmp was added to the list of valid mountpoints in the filesystem
customization step.
No validation is necessary at this time because rhel-86, centos-8, and
centos-9 all support a /tmp mountpoint.
Add error information for failed image
builds. The error details are only displayed
for failed builds and the error highest up
the error chain is displayed in the expandable
section of the image.
This workflow syncs the main branch with the stage-stable branch.
It also includes a production target which needs to be dispatched
manually. The production target pushes the input ref to both prod-beta
and prod-stable branches.
This results in the main branch always being deployed on stage-beta and
stage-stable, and the prod-beta and prod-stable branches being synced on
release.
This commit displays the UUID in an expandable details row. This is
necessary because if an image was named, the UUID was not displayed.
It is important that a user know the UUID for troubleshooting, for
example in the case of requesting help with an image.
To facilitate this, the original Table component was converted to a
TableComposable component. TableComposable is newer and recommended over
the older Table by PatternFly.
* devel: update composer config
Update some of the config for the docker-compose
file since there have been a few changes and the
config is slightly out of date. Additionally, a
refresh_token parameter was added to the oauth_url
since this is used by composer's mock openid provider
to generate the `rh-id-org` key in the jwt token.
* distribution: update frontend entrypoint
Update the command for spinning up the frontend
to match the new script command.
* devel: remove offline token
Remove the offline token and replace
with a client secret instead.
* devel: add metrics profile
Only launch the metrics containers when
explictly requested. This helps decrease
the logging output when the metrics are
not required. The metrics can be called
with `docker-compose --profile metrics up`
The distinction is made by checking if the distribution contained
'rhel'. This is the same way the review page determins if it should show
a registration tab.
Update the start scripts to match the updated scripts
in the `package.json`. Additionally, add instructions
for forwarding the domains to localhost for the stage
and prod since this is only mentioned in the `devel/`
readme.
Resolves#604. The available and chosen package search inputs now have a
reset button which resets the search and list elements to their default
states. This fixes a cosmetic issue related to the focus-visible width
being smaller than the search input width. This is accomplished by passing
an onClear prop to the search input.
The functions used to add all and selected packages were split from two
functions into four functions. The functions appear similiar but this is only
superficial; the logic is actually quite different and there is very
little code reuse. Four separate functions will be easier to understand and
maintain.
This commit includes several other modifications:
1. The chosen package search is now a typeahead filter. This brings it
in line with PatternFly dual list selector examples.
2. The available package search button has changed to be in line with
the PatternFly <SearchInput /> component examples.
3. Package sorting behavior is now consistent. Previously, packages would be
sorted if 'add all' was used but not if 'add selected' was used. Now
the default behavior is to always sort the package list.
The Details step is renamed to Name Image and moved to the last step
before Review. Also, the validation is removed since all utf-8
characters are supported for image names.
The default release script doesn't push `main` to stage-beta, so
reintroduce the custom_release script. This script is simplified
however, and doesn't push to the ci/qa environments as those aren't used
by image-builder anyway.
This got broken in #696, `deployment` never actually got set during the
release build process, and now we default to
`apps`. `frontend-components` will automatically do the right thing and
set the deployment based on the branch name.
It's important to have NODE_ENV=production during build time in travis,
as packages can have different build artifacts depending on the NODE_ENV
value.
Validation is not enforced on the image output step
when selecting and then deselecting an image type. This
is because the only validation which is set is `Required`.
However, after deselecting an image type the input becomes
a key-value object with all the values set to false. This
commit adds a custom validator to check that at least one
value in the object is set to true. Fixes#575
