-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default values for variables removed #539
Conversation
@ocofaigh can you please check and verify. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marifse I left one comment. Also adding @SirSpidey as reviewer for the wording you are adding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small editorial suggestions
@ocofaigh can you please check now, requested fixes have been addressed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Completing the description and referencing any issues might have helped understand. I did look for kms default issues and found none, but that may have been my search.
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
region and prefix values need to be added as TF_VARs in cra-config.yaml
now that they are required vars in the example being scanned.
@ocofaigh values for region and prefix in cra-config.yml have been added. |
cra-config.yaml
Outdated
@@ -4,6 +4,8 @@ CRA_TARGETS: | |||
- CRA_TARGET: "examples/complete" # Target directory for CRA scan. If not provided, the CRA Scan will not be run. | |||
CRA_IGNORE_RULES_FILE: "cra-tf-validate-ignore-rules.json" # CRA Ignore file to use. If not provided, it checks the repo root directory for `cra-tf-validate-ignore-rules.json` | |||
PROFILE_ID: "0e6e7b5a-817d-4344-ab6f-e5d7a9c49520" # SCC profile ID (currently set to the FSCloud 1.4.0 profile). | |||
TF_VAR_regions: "us-south" | |||
TF_VAR_prefix: "complete-kms" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are not in correct place in yaml. They need to be under CRA_ENVIRONMENT_VARIABLES
. See the commented out code below this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ocofaigh fixed.
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@marifse Looks like your PR contains an old version of the common-dev-assets git submodule, and so pipeline is failing. I suggest you don't commit updates to common-dev-assets to avoid this issue. Please follow the steps below:
Detected common-dev-assets git submodule commit ID is older than the one in primary branch. To fix:
1. Record the current state of the working directory:
i. git stash
2. Ensure that your local primary branch is up to date:
i. git checkout <master / main>
ii. git pull origin <master / main>
iii. git submodule update --rebase
3. Make sure your dev branch is rebased with remote primary branch:
i. git checkout <dev-branch>
ii. git stash pop
iii. git pull origin <master / main>
4. Run the following command to sync the git submodule with primary branch:
i. git submodule update --rebase
Description
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers