- Gracefully handle errors that are thrown during remove location script
- This should handle scenarios where the location is not found or not provided, as well as other error cases
Co-authored-by: Jonathan King <jonathankingfc@gmail.com>
* api: Removing parsing of datetime (PROJQUAY-5360)
* added ignoretz flag to date util parser
* added removed extra line
---------
Co-authored-by: Sunandadadi <sunanda.3094@gmail.com>
* config-tool: (247 commits)
chore: Move config-tool into its own directory
pg: Add warning log when Postgres version less than 13 (#218)
chore: Bump dependencies (PROJQUAY-5630) (#211)
build(deps): bump decode-uri-component in /pkg/lib/editor (#192)
chore: Create Quay PR from the same push event
chore: Use DEPLOY_PAT so that GitHub reacts on new tags
build(deps): bump socket.io-parser in /pkg/lib/editor (#213)
chore: Create PR against Quay for new tags (#212)
build(deps): bump minimist and karma in /pkg/lib/editor (#210)
deploy: use PAT for creating PR on quay repo (PROJQUAY-5048) (#207)
deploy: fix release.yaml quote (PROJQUAY-5048) (#206)
chore: Bump http-swagger (PROJQUAY-3643) (#198)
deploy: Create a PR against quay for every release (PROJQUAY-5048) (#204)
deploy: Add workflow to auto release on push (PROJQUAY-5048) (#200)
storage: Add CloudFlare and MultiCDN config validation (PROJQUAY-5048) (#199)
setup: Add ALLOWED_OCI_ARFICAT_TYPES to generated config (PROJQUAY-1032) (#110)
docs: Add documentation for TLS usage (PROJQUAY-4558) (#188)
Update mini-go (#184)
validator: Fix database.pem path in config.yaml (PROJQIUAY-4222) (#181)
ci: Update golang version in CI (PROJQUAY-1605)
...
In Clair 4.7, an API field documented to have version information in no
particular format may URL encode it. This change attempts to decode and
read a known field that contains the "fixed" version. If that fails, the
value will be passed through, as it is now.
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Co-authored-by: Hank Donnay <hdonnay@redhat.com>
* chore: Bump dependencies (PROJQUAY-5630)
* Bump minimal Go version to 1.19
* X.509 CommonName is deprecated in Go 1.15 and removed from 1.17
* chore: Workaround for dubious ownership issue
As we agreed to put the Jira ticket only into the commit title, we can
remove neofinancial/ticket-check-action and use only
conventional-commit-checker-action.
Co-authored-by: Oleg Bulatov <oleg@bulatov.me>
* oci: Allow optional properties in the config layer to be set to null
* Correct formatting
* oci: Allow optional components in the image config to be set to "null" See OCI spec for more information:
https://github.com/opencontainers/image-spec
---------
Co-authored-by: Ivan Bazulic <ibazulic@redhat.com>
* storage: make cloudfront_distribution_org_overrides optional (PROJQUAY-5788)
This is causing issues with config editor where it
configure CloudFront provider because of the required
override param
* fix black formatting
* fix tests
* fix black formatting
* fix tests
* fix tests
---------
Co-authored-by: Syed <syed@apache.org>
* Pagination: Fixing paginate for /api/v1/superuser/logs API
* using offset to fetch next page items
* adding datetime parsing
* using black to format code
* removing use_offset
* Removing redundant declaration
---------
Co-authored-by: Sunandadadi <sunanda.3094@gmail.com>
* chore: Create PR against Quay for new tags
* chore: Open PRs against Quay with non-default title
The default title is "Changes by create-pull-request action", which is
too generic.
(PROJQUAY-4659)
Change the default from `False` to `True` for
`FEATURE_SECURITY_SCANNING_NOTIFY_ON_NEW_INDEX`.
Since this flag addresses a bug, it should be enabled by default.
* displaying tag sizes as MB instead of MiB
* adding newline to end of file
* updating sizes from base 1000 to 1024
---------
Co-authored-by: bcaton <bcaton@redhat.com>
- Features must be initialized in order to check if storage replication is enabled, so we need to import and intialize the config from inside the util script
Co-authored-by: Jonathan King <jonathankingfc@gmail.com>
- This removes first the ImageStoragePlacements that are associated with the location
- Once those are cleaned up, the ImageStorageLocation itself is removed from the database
Co-authored-by: Jonathan King <jonathankingfc@gmail.com>
