Skip to content

allow non target access actors to check, compose, delete and publish schemas #18200

allow non target access actors to check, compose, delete and publish schemas

allow non target access actors to check, compose, delete and publish schemas #18200

Triggered via pull request January 31, 2025 15:22
Status Failure
Total duration 17m 15s
Billable time 19m
Artifacts 8

pr.yaml

on: pull_request
Matrix: build / build-and-dockerize
graphql-breaking-changes  /  search-token
0s
graphql-breaking-changes / search-token
db-types  /  diff
1m 9s
db-types / diff
test  /  db-migrations
1m 24s
test / db-migrations
test  /  unit
2m 1s
test / unit
code-style  /  eslint-and-prettier
3m 18s
code-style / eslint-and-prettier
typescript  /  typecheck
4m 21s
typescript / typecheck
website-preview  /  deployment
7s
website-preview / deployment
storybook-preview  /  deployment
5s
storybook-preview / deployment
release-candidate  /  snapshot
release-candidate / snapshot
Matrix: static-analysis / analyze
build  /  publish multiarch manifest
1m 3s
build / publish multiarch manifest
Matrix: alpha / cli-test
alpha  /  Extract CLI version
0s
alpha / Extract CLI version
graphql-breaking-changes  /  check
8s
graphql-breaking-changes / check
Matrix: test / integration
alpha  /  ...  /  Build CLI Docker Image
alpha / publish_docker / Build CLI Docker Image
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 27 warnings
tests/cli/schema.spec.ts > schema:publish with --target parameter matching the access token (UUID): integration-tests/tests/cli/schema.spec.ts#L409
AssertionError: promise rejected "Error: Command failed with exit code 2: /… { …(12) }" instead of resolving ❯ tests/cli/schema.spec.ts:409:5 Caused by: Caused by: Error: Command failed with exit code 2: /home/runner/work/console/console/packages/libraries/cli/bin/run schema:publish --registry.endpoint http://localhost:8082/graphql --registry.accessToken e9a43cfe3619f1c89ada2a41045b28b4 --author Kamil --target 10a066f9-9eeb-43a2-9406-00d8ae831e4d fixtures/init-schema.graphql › Error: Unexpected error. (Request ID: › "CQrck614QE6AoVqGHleyTw/0000000507") [115] › > See https://the-guild.dev/graphql/hive/docs/api-reference/cli#errors for › a complete list of error codes and recommended fixes. › To disable this message set HIVE_NO_ERROR_TIP=1 › Reference: CQrck614QE6AoVqGHleyTw/0000000507 ❯ makeError ../node_modules/.pnpm/@esm2cjs[email protected]/node_modules/@esm2cjs/execa/esm/lib/error.js:59:11 ❯ handlePromise ../node_modules/.pnpm/@esm2cjs[email protected]/node_modules/@esm2cjs/execa/esm/index.js:119:26 ❯ exec testkit/cli.ts:23:18 ❯ Module.schemaPublish testkit/cli.ts:40:10 ❯ tests/cli/schema.spec.ts:399:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { shortMessage: 'Command failed with exit code 2: /home/runner/work/console/console/packages/libraries/cli/bin/run schema:publish --registry.endpoint http://localhost:8082/graphql --registry.accessToken e9a43cfe3619f1c89ada2a41045b28b4 --author Kamil --target 10a066f9-9eeb-43a2-9406-00d8ae831e4d fixtures/init-schema.graphql', command: '/home/runner/work/console/console/packages/libraries/cli/bin/run schema:publish --registry.endpoint http://localhost:8082/graphql --registry.accessToken e9a43cfe3619f1c89ada2a41045b28b4 --author Kamil --target 10a066f9-9eeb-43a2-9406-00d8ae831e4d fixtures/init-schema.graphql', escapedCommand: '"/home/runner/work/console/console/packages/libraries/cli/bin/run" "schema:publish" --registry.endpoint "http://localhost:8082/graphql" --registry.accessToken e9a43cfe3619f1c89ada2a41045b28b4 --author Kamil --target 10a066f9-9eeb-43a2-9406-00d8ae831e4d "fixtures/init-schema.graphql"', exitCode: 2, signal: undefined, signalDescription: undefined, stdout: '', stderr: ' › Error: Unexpected error. (Request ID: \n › "CQrck614QE6AoVqGHleyTw/0000000507") [115]\n › > See https://the-guild.dev/graphql/hive/docs/api-reference/cli#errors for\n › a complete list of error codes and recommended fixes.\n › To disable this message set HIVE_NO_ERROR_TIP=1\n › Reference: CQrck614QE6AoVqGHleyTw/0000000507', failed: true, timedOut: false, isCanceled: false, killed: false }
tests/cli/schema.spec.ts > schema:publish fails with --target parameter not matching the access token (slug): integration-tests/tests/cli/schema.spec.ts#L430
Error: Snapshot `schema:publish fails with --target parameter not matching the access token (slug) 1` mismatched - Expected + Received @@ -1,10 +1,10 @@ :::::::::::::::: CLI FAILURE OUTPUT ::::::::::::::: exitCode------------------------------------------: 2 stderr--------------------------------------------: - › Error: No access (reason: "Missing permission for performing + › Error: No access (reason: "Missing permission for performing › 'schemaVersion:publish' on resource") (Request ID: __REQUEST_ID__) [115] › > See https://__URL__ for › a complete list of error codes and recommended fixes. › To disable this message set HIVE_NO_ERROR_TIP=1 › Reference: __ID__ ❯ tests/cli/schema.spec.ts:430:5
test / integration (2)
Process completed with exit code 1.
test / integration (3)
The job was canceled because "_2" failed.
test / integration (3)
The operation was canceled.
test / integration (1)
The job was canceled because "_2" failed.
test / integration (1)
The operation was canceled.
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
alpha / npm / snapshot
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
static-analysis / analyze (javascript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
static-analysis / analyze (javascript)
Unable to validate code scanning workflow: MissingPushHook
static-analysis / analyze (typescript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
static-analysis / analyze (typescript)
Unable to validate code scanning workflow: MissingPushHook
Variables should be defined before their use: docker/services.dockerfile#L13
UndefinedVar: Usage of undefined variable '$RELEASE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: docker/services.dockerfile#L21
UndefinedVar: Usage of undefined variable '$RELEASE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: docker/services.dockerfile#L22
UndefinedVar: Usage of undefined variable '$PORT' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L11
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/services.dockerfile#L14
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/services.dockerfile#L21
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L10
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/services.dockerfile#L12
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/migrations.dockerfile#L12
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/migrations.dockerfile#L15
UndefinedVar: Usage of undefined variable '$IMAGE_TITLE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: docker/services.dockerfile#L22
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Variables should be defined before their use: docker/migrations.dockerfile#L12
UndefinedVar: Usage of undefined variable '$RELEASE' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Variables should be defined before their use: docker/migrations.dockerfile#L17
UndefinedVar: Usage of undefined variable '$IMAGE_DESCRIPTION' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/

Artifacts

Produced during runtime
Name Size
graphql-hive~console~N1D02Q+13.dockerbuild
1.27 MB
graphql-hive~console~XF8SXO+13.dockerbuild
2.22 MB
hive-cli-darwin-arm64
41.9 MB
hive-cli-darwin-x64
42.5 MB
hive-cli-linux-arm
42.4 MB
hive-cli-linux-x64
47.3 MB
hive-cli-win-x64
37.5 MB
hive-cli-win-x86
34.9 MB