⚠️ CONFLICT! Lineage pull request for: skeleton #30

cisagovbot · 2024-12-11T00:38:57Z

Lineage Pull Request: CONFLICT

Lineage has created this pull request to incorporate new changes found in an
upstream repository:

Upstream repository: https://github.com/cisagov/skeleton-packer.git
Remote branch: HEAD

Check the changes in this pull request to ensure they won't cause issues with
your project.

The lineage/skeleton branch has one or more unresolved merge conflicts
that you must resolve before merging this pull request!

How to resolve the conflicts

Take ownership of this pull request by removing any other assignees.

Clone the repository locally, and reapply the merge:

git clone git@github.com:cisagov/ubuntu-server-packer.git ubuntu-server-packer
cd ubuntu-server-packer
git remote add skeleton https://github.com/cisagov/skeleton-packer.git
git remote set-url --push skeleton no_push
git switch develop
git switch --create lineage/skeleton --track origin/develop
git pull skeleton HEAD
git status

Review the changes displayed by the status command. Fix any conflicts and
possibly incorrect auto-merges.
After resolving each of the conflicts, add your changes to the
branch, commit, and push your changes:
```
git add README.md ansible/cloud_init.yml ansible/example.yml ansible/harden.yml ansible/post_setup.sh ansible/ufw.yml src/packer.pkr.hcl src/version.txt 
git commit
git push --force --set-upstream origin lineage/skeleton
```
Note that you may append to the default merge commit message
that git creates for you, but please do not delete the existing
content. It provides useful information about the merge that is
being performed.
Wait for all the automated tests to pass.
Confirm each item in the "Pre-approval checklist" below.
Remove any of the checklist items that do not apply.
Ensure every remaining checkbox has been checked.
Mark this draft pull request "Ready for review".

✅ Pre-approval checklist

✌️ The conflicts in this pull request have been resolved.
All future TODOs are captured in issues, which are referenced in code comments.
All relevant type-of-change labels have been added.
All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
Tests have been added and/or modified to cover the changes in this PR.
All new and existing tests pass.

Note

You are seeing this because one of this repository's maintainers has
configured Lineage to open pull requests.

For more information:

🛠 Lineage configurations for this project are stored in .github/lineage.yml

📚 Read more about Lineage

This commit will make a few changes. The orginal version of the semantic checking function was a bit more difficult to read. It is now somewhat easier to follow how the regex is structured. Also the function has been renamed to check_python_version since it has 2 functions, making sure that the version is semantically correct and the second is to make sure that it is installed on the user's machine. This makes it easier to follow the logic for the flags, -p or --python-version and -l or --list-versions

…ttps://github.com/cisagov/skeleton-generic into improvement/correct-semantic-python-version-checks

Co-authored-by: dav3r <david.redmin@trio.dhs.gov>

Add the `check-useless-excludes` meta hook to verify that any defined `exclude` directives apply to at least one file in the repository.

Instead of manually installing Packer we can instead leverage the hashicorp/setup-packer Action just as we do for Terraform.

He is no longer a member of @cisagov/vm-dev.

Previously we only provided a lower bound for the version, but pinning to a specific version aligns with what has been done with the prettier hook and how pre-commit hooks are pinned in general. The flake8-docstrings package is rarely updated, so there is no real downside to pinning to a specific version. Co-authored-by: Nick <50747025+mcdonnnj@users.noreply.github.com>

Bumps [actions/cache](https://github.com/actions/cache) from 3 to 4. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@v3...v4) --- updated-dependencies: - dependency-name: actions/cache dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

Bumps [crazy-max/ghaction-github-status](https://github.com/crazy-max/ghaction-github-status) from 3 to 4. - [Release notes](https://github.com/crazy-max/ghaction-github-status/releases) - [Commits](crazy-max/ghaction-github-status@v3...v4) --- updated-dependencies: - dependency-name: crazy-max/ghaction-github-status dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

This is done automatically with the `pre-commit autoupdate` command. The pre-commit/mirrors-prettier hook was manually held back because the latest tags are for alpha releases of the next major version.

Use the latest v3 release available from NPM.

…max/ghaction-github-status-4 Bump crazy-max/ghaction-github-status from 3 to 4

…s/cache-4 Bump actions/cache from 3 to 4

Use an Action to install Packer in our GitHub Actions workflows

…hon-version-checks Add checks for correct semantic version of Python

@jasonodoom

Remove @jasonodoom as a codeowner

The pip-audit tool will audit any supplied pip requirements files for vulnerable packages.

…hook Add the `check-useless-excludes` hook to the pre-commit configuration

…mmit_hook Add a pre-commit hook to run `pip-audit`

Copy over necessary changes from the `bump_version.sh` script.

This functionality has been replaced by the `bump-version` script.

…script Replace the `bump_version.sh` script

There is no reason to have any information but the version in the version tracking file for Packer template projects. The current format is simply an artifact of mirroring things over from the cisagov/skeleton-python-library project.

The src directory no longer exists.

…format Change the format of the version tracking file

…-build-commands Use the correct `packer build` commands

…keleton

Instead insert a shellcheck directive comment at the top of the script.

This script belongs with the rest of the Packer code.

Michael Saki and others added 30 commits February 14, 2024 12:59

Add checks for semantic python versions

33582a1

Add checks for semantic python versions

cea8edc

Merge branch 'improvement/correct-semantic-python-version-checks' of h…

f7b9d05

…ttps://github.com/cisagov/skeleton-generic into improvement/correct-semantic-python-version-checks

Remove example of correct semantic version

327ab73

Refactor the error message for the user

4dedf50

Improve the semantic error message

e84deea

Fix grammar

5fdc7be

Co-authored-by: dav3r <david.redmin@trio.dhs.gov>

Refactor regex, add link, and improve comments

42ef8c2

Update link to use semver.org over regex101.com

a77e5e1

Remove unnecessary period

5fe14c7

Co-authored-by: dav3r <david.redmin@trio.dhs.gov>

Add a meta hook to the pre-commit configuration

b7896a0

Add the `check-useless-excludes` meta hook to verify that any defined `exclude` directives apply to at least one file in the repository.

Remove exclude directive that does not apply to any files

260566f

Add a lower-bound pin for flake8-docstrings

a68994d

Use the hashicorp/setup-packer GitHub Action

43b91c7

Instead of manually installing Packer we can instead leverage the hashicorp/setup-packer Action just as we do for Terraform.

Remove @jasonodoom as a codeowner

8ada75d

He is no longer a member of @cisagov/vm-dev.

Update pre-commit hook versions

6a58c2c

This is done automatically with the `pre-commit autoupdate` command. The pre-commit/mirrors-prettier hook was manually held back because the latest tags are for alpha releases of the next major version.

Manually update the prettier hook

553efcb

Use the latest v3 release available from NPM.

Merge pull request #170 from cisagov/dependabot/github_actions/crazy-…

184e749

…max/ghaction-github-status-4 Bump crazy-max/ghaction-github-status from 3 to 4

Merge pull request #171 from cisagov/dependabot/github_actions/action…

d99c117

…s/cache-4 Bump actions/cache from 3 to 4

Merge pull request #187 from cisagov/improvement/use_setup_packer_action

2491ca0

Use an Action to install Packer in our GitHub Actions workflows

Merge pull request #176 from cisagov/improvement/correct-semantic-pyt…

f6c9537

…hon-version-checks Add checks for correct semantic version of Python

Merge pull request #188 from cisagov/remove-odoom-as-a-codeowner

10e5f6f

Remove @jasonodoom as a codeowner

Add a pre-commit hook to run pip-audit

045a998

The pip-audit tool will audit any supplied pip requirements files for vulnerable packages.

Merge pull request #178 from cisagov/improvement/add_pre-commit_meta_…

28dc4ce

…hook Add the `check-useless-excludes` hook to the pre-commit configuration

Merge pull request #179 from cisagov/improvement/add_pip-audit_pre-co…

5801cec

…mmit_hook Add a pre-commit hook to run `pip-audit`

mcdonnnj and others added 7 commits December 10, 2024 09:00

Pull in the bump-version script from cisagov/pre-commit-packer

2db3797

Modify the bump-version script for this repository

50bdadc

Copy over necessary changes from the `bump_version.sh` script.

Remove the bump_version.sh script

8c2b384

This functionality has been replaced by the `bump-version` script.

Merge pull request #377 from cisagov/improvement/update_bump_version_…

a54a55d

…script Replace the `bump_version.sh` script

Change the format of the version tracking file

4934005

There is no reason to have any information but the version in the version tracking file for Packer template projects. The current format is simply an artifact of mirroring things over from the cisagov/skeleton-python-library project.

Correct reference to src directory in setup-env

a368704

The src directory no longer exists.

Merge pull request #379 from cisagov/improvement/change_version_file_…

eb4508a

…format Change the format of the version tracking file

cisagovbot assigned dav3r, felddy, jsf9k and mcdonnnj Dec 11, 2024

cisagovbot added the upstream update This issue or pull request pulls in upstream updates label Dec 11, 2024

jsf9k and others added 2 commits December 11, 2024 14:07

Use the correct packer build commands

a770f2b

Merge pull request #384 from cisagov/documentation/use-correct-packer…

82a9528

…-build-commands Use the correct `packer build` commands

jsf9k unassigned felddy, dav3r and mcdonnnj Dec 13, 2024

jsf9k added 3 commits December 13, 2024 14:43

Merge remote-tracking branch 'skeleton-packer/develop' into lineage/s…

906a5e8

…keleton

Remove needless shebang

1e10476

Instead insert a shellcheck directive comment at the top of the script.

Move post_script.sh to the main project directory

6bd2527

This script belongs with the rest of the Packer code.

jsf9k force-pushed the lineage/skeleton branch from fa2d5c3 to 6bd2527 Compare December 13, 2024 19:49

Update terraform-docs output

db801c5

jsf9k force-pushed the lineage/skeleton branch from 66be1bc to db801c5 Compare December 19, 2024 19:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

⚠️ CONFLICT! Lineage pull request for: skeleton #30

⚠️ CONFLICT! Lineage pull request for: skeleton #30

cisagovbot commented Dec 11, 2024 •

edited by jsf9k

Loading

⚠️ CONFLICT! Lineage pull request for: skeleton #30

Are you sure you want to change the base?

⚠️ CONFLICT! Lineage pull request for: skeleton #30

Conversation

cisagovbot commented Dec 11, 2024 • edited by jsf9k Loading

Lineage Pull Request: CONFLICT

How to resolve the conflicts

✅ Pre-approval checklist

cisagovbot commented Dec 11, 2024 •

edited by jsf9k

Loading