AWS CodeBuild fails - need node installed

[fossell]

Describe the Problem

The github action for AWS CodeBuild failed for PR #92 which updates documentation from fossell fork. Build phase with error: COMMAND_EXECUTION_ERROR: Error while executing command: npm install. Reason: exit status 254 Suggests the need to install node in the AMI. Should also note this error when pushing the ug_update branch to fossell fork after merging develop branch: ! [remote rejected] update_ug -> update_ug (refusing to allow a Personal Access Token to create or update workflow.github/workflows/documentation.ymlwithoutworkflowscope) error: failed to push some refs to 'https://github.com/fossell/wrfcloud'

Recent PR #93 was successful in the CodeBuild tests, so might be issue related to PAT?

Expected Behavior

AWS CodeBuild github action should pass when activated for PR. It does for #93, but not for #92.

Environment

Describe your runtime environment: 1. Machine: AWS wrfcloud AMI 2. OS: wrfcloud AMI 3. Branch: from fossell fork, branch ug_update

To Reproduce

Describe the steps to reproduce the behavior: Unsure how to reproduce.

Relevant Deadlines

December 5, 2022

Define the Metadata

Assignee

• [ ] Select engineer(s) or no engineer required
• [ ] Select scientist(s) or no scientist required

Labels

• [ ] Select component(s)
• [ ] Select priority

Projects and Milestone

• [ ] Select first Project for support of the current release
• [ ] Select second Project for development toward the next official release
• [ ] Select Milestone as the next bugfix version

Bugfix Checklist

• [ ] Complete the issue definition above, including the Time Estimate and Funding Source.
• [ ] Fork this repository or create a branch of main_\. Branch name: bugfix_<Issue Number>/main_<Version>_<Description>
• [ ] Fix the bug and test your changes.
• [ ] Add/update log messages for easier debugging.
• [ ] Add/update tests.
• [ ] Add/update documentation.
• [ ] Push local changes to GitHub.
• [ ] Submit a pull request to merge into main_\. Pull request: bugfix <Issue Number> main_<Version> <Description>
• [ ] Define the pull request metadata, as permissions allow. Select: Reviewer(s) and Development issue Select: Project for support of the current release Select: Milestone as the next bugfix version
• [ ] Iterate until the reviewer(s) accept and merge your changes.
• [ ] Delete your fork or branch.
• [ ] Complete the steps above to fix the bug on the develop branch. Branch name: bugfix_<Issue Number>/develop_<Description> Pull request: bugfix <Issue Number> develop <Description> Select: Reviewer(s) and Development issue Select: Project for the next official release Select: Milestone as the next official version
• [ ] Close this issue.

[fossell]

@JohnHalleyGotway - See the text of this issue. When I merged the develop branch into my local branch of my fork, and then pushed my local branch to my forked repo, there was a warning about access tokens. Maybe that's the issue?