Add v4 sub-folder so this module could run with AzureRM provider both v3 and v4.
#586
Triggered via pull request
September 10, 2024 01:14
lonegunmanb
Status
Success
Total duration
6m 48s
Artifacts
–
pr-check.yaml
on: pull_request
prepr-check
/
prepr-check
6m 38s
Annotations
4 warnings
|
prepr-check / prepr-check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@f43a0e5ff2bd294095638e18286ca9a3d1956744, actions/setup-go@6edd4406fa81c3da01a34fa6f6343087c207a568. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
prepr-check / prepr-check
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
|
|
prepr-check / prepr-check
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.16.5.
|
|
prepr-check / prepr-check
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.
|