Skip to content

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope #539

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope

fix: prevent assigning incorrect resource ID for sensitive variables with same name, type and at least one matching scope #539

Triggered via pull request February 15, 2024 09:46
Status Success
Total duration 19s
Artifacts

revive-lint.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build: internal/errors/error.go#L1
should have a package comment
build: internal/errors/error.go#L13
parameter 'ctx' seems to be unused, consider removing or renaming it as _
build: internal/errors/error.go#L19
func ProcessApiError should be ProcessAPIError
build: internal/projects/extension_settings.go#L12
comment on exported function ExpandJiraServiceManagementExtensionSettings should be of the form "ExpandJiraServiceManagementExtensionSettings ..."
build: internal/projects/extension_settings.go#L1
should have a package comment
build: internal/errors/error.go#L19
exported function ProcessApiError should have comment or be unexported
build: internal/errors/error.go#L13
exported function DeleteFromState should have comment or be unexported
build: internal/test/channel_test_options.go#L1
should have a package comment
build: internal/projects/extension_settings.go#L23
comment on exported function ExpandServiceNowExtensionSettings should be of the form "ExpandServiceNowExtensionSettings ..."
build: internal/test/project_test_options.go#L15
exported type ProjectTestOptions should have comment or be unexported